Yes, seriously. So by your logic we should be listing the browsers, the operating systems, the compilers, the linkers.
No. The title is misleading, I clicked on it expecting a good breakdown of the current can't-do-without javascript libraries for web application programming.
MongoDB? PostgreSQL? Why don't we mention Python too since not every Javascript programmer is using NodeJS, oh wait - maybe we should start mentioning Haskell to JS compilers too, yes, because those are Javascript tools and libraries.
All of those things are interesting but the title mislead me and I made note of it.
>MongoDB? PostgreSQL? Why don't we mention Python too since not every Javascript programmer is using NodeJS, oh wait - maybe we should start mentioning Haskell to JS compilers too, yes, because those are Javascript tools and libraries.
I don't understand this slippery slope argument. One can mention tools relevant to JS developent that are not themselves written in JS, without going to the extreme of listing everything under the sun.
Even if it's a little fuzzy when you stop, MongoDB is known to be a great tool for NodeJS projects, whereas everybody understands that the linker and the compiler is not really relevant to the discussion.
It's pretty easy to understand and it's not a slippery slope; what is slippery is bringing in tools and libraries that have nothing to do with Javascript.
Also, this whole argument has gone on far more than I intended - simply pointing out that the title was misleading and the reason why I thought it was misleading has suddenly turned into a holy jihad (proof given by the downvoters) to defend MongoDB's inclusion in the list (which is sad because MongoDB isn't a great DB either but that's not part of this argument).
I hold on to the fact, though, that it was indeed misleading and my desire for clarity is important to me and meaningful writing; when people criticize my writing for the smallest or the largest of reasons I want to hear it. Misleading title? Okay, why and what would you suggest?
In my classes, I've found a lot of problems with Postgres.app. It definitely works for some, but not as reliably as home-brew. It depends on how your machine is set up. I needed a foolproof, repeatable process for students to follow, so that's why I wrote this article.
