Thanks! And yeah we can put an empty line to break off into a new category. So essentially it's one category per paragraph. Within a paragraph, there can be sub-categories one level deep. You can also put tags inline.
I'm still trying to figure out how to allow nesting categories an arbitrary number of levels deep. But I don't want to introduce extra symbols and stuff, it'll be too much complexity too early on. I can imagine that for most cases, headings, sub-headings and inline tags are enough.
I will allow more customisation soon, such as using multiple heading identifiers. I'll add features as the need arises. I haven't used it for very long myself.
My naive initial assumption (just due to my own bias) was that nesting would work the same way as in Markdown – i.e., that the number of `#`’s indicates the heading level.
Maybe worth for you to consider? It’s a well known convention, it should be fairly self-explanatory, and it would work independent of the notion of paragraphs.
# animals
elephant
## felines
cats
# plants
apple tree
## flowers
lily
I've been programming in JS for years now and only picked up clojure last september. I love it. I started with "Clojure for the Brave and True" and then went on to solve codewars challenges and make web apps in clojurescript.
I completely agree with your point about learning something different. Clojure is really good at handling immutable data, lazy evaluation, macros. So you can write elegant code that would be inefficient/unweildy in something like js or python
Suppose there are several different major components of a large system that need to know something about an important entity like a user for example. A good way to share that information is to have a user service that answers those questions (in a larger system) or a user library/data provider that does this (in a smaller system). A worse way to do that is to have sql queries that different systems use to get that data.
It’s one less layer, so yes. But going thru a service gives you the opportunity to use caching, cache invalidation, or switch the operation to different kind of data store. So potentially it can be faster sometimes. Also if the database is occasionally burning up from being overworked then survival and reliability are much more important than speed.
A service layer is also a single point of failure. So if uptime is a concern, one less component that a developer can accidentally take out and bring down the whole system is valuable.
One of the most pernicious dangers in shipping a successful project is you paradoxically both cargo cult and critique random parts of your success. Looking back, you might decide that choice A was correct, while choice B was incorrect. But you don't have the benefit of having tried all of those other options. So don't trust postmortems too much, they are single data points in a sea of failures. They could very well be random chance.
I think you should just spend a significant amount of time in both languages and over time you’ll be all good.
I programmed in JS for a year before picking up python. I would struggle with python’s syntax for a while but over time it just worked out. Same thing now with clojure.
I think it’s the same as being bilingual. Your brain just switches effortlessly given enough practice
I'm still trying to figure out how to allow nesting categories an arbitrary number of levels deep. But I don't want to introduce extra symbols and stuff, it'll be too much complexity too early on. I can imagine that for most cases, headings, sub-headings and inline tags are enough.
I will allow more customisation soon, such as using multiple heading identifiers. I'll add features as the need arises. I haven't used it for very long myself.