ppj606

Novel idea to reward hiring companies for exhibiting good behaviours - surely this will be easily gamed though?

The usage and access of data in your data store when building a realtime application. If you were building a chat-app these days you are given a number of very easy to adopt (minimal complexity/edge cases) NoSQL solutions - Firebase, Parse, RethinkDB.

Whereas with SQL you have the option of using cache layers (which you could say is NoSQL anyway), message queues, naive timely polling and log monitoring.

With NoSQL the solutions are just simpler. For example Firebase has a tutorial for creating a real-time chat [1] - it takes 5 minutes.

[1] https://www.firebase.com/tutorial/#example/chat

With the rise of realtime applications I'd argue that the situations for using NoSQL for the common project are growing.

I think the author of the post has made a good point, that many seem to forget - it is always a trade-off whichever tool you use.

Outperform on what? Can you give specific examples? There are a large number of Combinatorial Optimisation Problems. It is a very sweeping statement to say 'gradient descent techniques far outperform evolutionary ones'.

I wouldn't say they are bad idea verbatim, but as they do not have good browser support, it is currently bad practice to rely upon them.

I certainly won't be swaying from using Sass and the other various benefits you get from a pre-processor. As you say - right now it's a no brainer.