Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

unpopular opinion, but the reason people chose node.js is because for some dense folks like me it's easier to reason about and understand how everything works. the tooling is abysmal compared to rails, django & laravel. but at least I know how my app works from top to bottom. you take a productivity hit in your first node.js project but after that you would've collected / curated your own personal tools/libraries. and hell yeah spinning an api that does whatever you want is easy as hell. much respect to dhh though


I’m not sure your opinion is unpopular, but I have a hard time following your logic. Isn’t part of why a solid and curated framework makes perfect sense (and make you more productive) exactly that you don’t have to understand everything that’s going on?

I have a decent understanding of what lies beneath linq in C# for instance, but that’s because I’m curious by nature and not because I had to know it to utilise it. I mean, I guess you could argue that people should know what’s going on, but the truth is that 90% of software development doesn’t require you to, if you pick the right tools.

I think this is a primary reason node.js never really picked up. No one wants to spend time building and maintain the wheel when you can get a trusted entity to do it for you. You may find the part about node not picking up odd, but if I look at job-listings for my entire country there is almost zero postings for a node backend.


But by the time "you would've collected / curated your own personal tools/libraries", you could have learned how Rails works.


If that's your concern, you can learn how the internals of rails (or django) work. Not being forced to do that doesn't mean you can't do it regardless :)




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: