4 ms·

I agree with you, but I suspect (not a node dev) the reason people talk this way is that almost everyone uses Express as their server, and a lot of people use N

• mercer 11y ago
  That's exactly how I'm using Node currently. While RoR would be smarter and faster if budget/time was an issue, I currently have the luxury of building a relatively simple site+CMS for a client with total freedom and a lot of time on my hands. After battling Rails' conventions and getting a bit sick of learning a lot of things that are only useful in the Rails world, I figured it might be nice to do everything almost from scratch (Express.js as a shortcut though). I'm using RethinkDB without an ORM, although over time I suspect my approach will become more ORM-like over time and I might just switch to one of the existing RethinkDB ORM's. It's loads of fun being able to understand most steps of the process of building a complete website that includes authentication, a database, a CMS, and whatnot, especially after relying on Rails' magic for a lot of things. I guess I just really prefer the explicitness of it all. That said, if money and/or time were an issue, or if the end product would have to be worked on by other developers, I'd probably go for RoR or Django. The amount of stuff it 'just' takes care of is much more than one might assume at first, and the amount of pitfalls in the category 'not knowing what you don't know' are not insignificant (XSS, for example).