It's actually commonly used in production for certain types of databases. SQLite is not a replacement for something such as postgresql but it certainly has it's use cases.
The use case for SQLite isn't high traffic public facing webpages. Here is their own list of 'famous' users: https://www.sqlite.org/famous.html
Every iPhone, and Android phone have SQLite running on them, which easily makes it the most used production database. It's use case is typically very low traffic websites or as client side storage.
Maybe I'm missing something but is Mongo in use on the client side in that same way? If not then SQLlite is being shoehorned into the discussion and the context in which production was used should be clear. I feel like people are trying to be technically right instead of following the actual discussion. I never meant client side software and definitely didn't mean someone's micro traffic blog, where a toy database could be used.
It is interesting how much penetration SQLlite has on the client, though.
At any rate, I know better than to not be extremely specific so I brought this on myself.
It seems like there have just been some assumptions going both ways.
This all started when someone trashed RDBMS for being "heavy", implying that Mongo is good because it's light.
Why would you care how heavy a DB is if it's not on the client side? The kind of memory and storage you need for even the heaviest popular RDBMS (MySQL?) is still low enough that's nearly free to create a small app.
Unfortunately that's not how your article has been interpreted, especially not in the reddit thread which has (predictably) divulged into an incoherent MongoDB hate-fest.
Leading questions, I'm afraid. Yes, equality is still broken, maps are broken (and in new & interesting ways in EMCAScript 6), and the language is occasionally whitespace-sensitive.
JavaScript was hastily designed, has never recovered, and shows no sign of ever fixing the fundamental problems. :-(
Case sensitivity i'm assuming you mean the automatic semi-colon insertion due to a line break after a return statement? I have a hard time seeing this as being a reason to dislike an entire language.
Most languages have features to avoid, JavaScript is no different. Many JavaScript developers use linters to avoid the poor `==` feature. I'm unfamiliar with the argument of the `Map` datastructure implementation being broken. Do you have a reference to that claim?
You criticize people for _premature optimization_ while in the same breath advocating rolling your own, shitting implementation for page views? Right...
This thread has been stormed by people who work in the sys admin space and either don't care to learn the technology, have used it unsuccessfully while it was young, or see it as harmful to their career.
HN tech hivemind is often both conservative and arrogant: node is an aberration, atom is a travesty, docker is for the lazy, front end frameworks are overused, etc etc.
Very true. The fact is, even very intelligent people tend to stick with ideas that were popular as they 'grew' into their position.
Programming is young, but if you look at the history of more developed fields such as physics and mathematics, there is a very long history of extremely respected scientists out right rejecting new theories for being outlandish and ridiculous that we now accept as the bedrock of scientific theory.
The truth is, just as with physics and mathematics, in computer science new ideas do form, but older generations rarely adapt, and it's only with death of the old, and the growth of a new generation do ideas become accepted.
