One of the many joys of working with Clojure https://clojure.org/guides/threading_macros
HN user
ds_
Not sure why you're being downvoted, because you're absolutely right.
The execute function can recognize it as a t-string and prevent SQL injection if the name is coming from user input. f-strings immediately evaluate to a string, whereas t-strings evaluate to a template object which requires further processing to turn it into a string.
Documentation (and press releases/FAQs) are usually for users. Specifications are for developers. The former can precede and help with forming the latter.
Limits have been proposed for how many of these stable relationships it's possible to maintain: https://en.wikipedia.org/wiki/Dunbar%27s_number
It's only not a valid point of criticism if you believe any level of wealth is justified as it must be proportional to that individual's contributions to society.
"Simple is often erroneously mistaken for easy. 'Easy' means 'to be at hand', 'to be approachable'. 'Simple' is the opposite of 'complex' which means 'being intertwined', 'being tied together'" - https://www.infoq.com/presentations/Simple-Made-Easy/
"Om Next is meant to be paired with Datomic" - although datomic makes some things easier, Om Next has no opinion on what backend you use.
ClojureScript can do this along with dead-code elimination / cross module code motion: http://swannodette.github.io/2015/02/23/hello-google-closure...
Here it is on Google maps: https://goo.gl/maps/6kZfb
That's fine if you're happy losing potential productivity gains from new features or community projects that tend to use the latest and greatest.
Are there any promising open source alternatives with similar philosophies to datomic?
This is also something I'm curious about, particularly how migrations are managed within a team. Most of the solutions I've seen require writing plain SQL in migration files which you name yourself. It's simple but I miss the productivity of DjangoORM or ActiveRecord for example. Or do most people use a schema-less database?
Can the improvements in loading time be attributed to angular alone?
And I bet most people can give you several. Can't remember the last time I bought a DVD or vinyl record, without having enjoyed it somewhere else first, for free.
It's the first result for "om clojurescript". So not really.
I can't see the parallels between js/html and css/html. React disregards the js/html because they acknowledge that there never really was proper separation. With css/html, at least to me, it seems like there is a clearer separation. Maybe I'm being shortsighted.
I'm wondering if the two projects are aware of each other and if there is the possibility for some collaboration there(similar ideas/approaches?)?
Why would you want to bundle styles with your components? There is already a nice separation there, maybe you could give an example use case?
Python has had generators since 2.2, where as they are just landing in js/node.js.
An interesting read on the subject: http://www.amazon.com/The-Unfolding-Language-Evolutionary-In...
Wikipedia gives an explanation: http://en.wikipedia.org/wiki/Yoda_conditions Seems kind of meh, especially if you're writing javascript when keywords like undefined can be redefined with no effect.
A similar convention, often seen within the node community: https://npmjs.org/doc/coding-style.html#Comma-First Personally, I find this ugly with very little benefit. It seems awkward to edit.
It does seem strange, is there a reasoned argument for why this can be better?
What do you mean by that? if (constant == variable) type conditions?
If express was connect, since koa is basically a rewrite of connect using generators, doesn't it make sense to give it a new name?
One way: It leverages generators, which helps in avoiding callback hell (http://blog.alexmaccaw.com/how-yield-will-transform-node) Koa is written by the same author as express.
That's pretty much what they did (and connect, which was the foundation of express and since bought by senchalabs).