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

Like, if you decide to do your backend in rust or python you can choose async or synchronous approaches - but Node locks you into async. I'm not a node developer so I can't sing the praises of what you get, but being locked into JavaScript's process model, VM, and type system is certainly a downside (for which you get the whole JS world). It's another example of...if you are architecting your service and you pick this you are picking some built in trade-offs.


maybe I don't understand something but most if not all node methods have their sync counterparts


You're thinking about JavaScript but I am talking about Node, which fundamentally uses a single-threaded approach[1] to great effect.

[1] https://stackoverflow.com/questions/17959663/why-is-node-js-...




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

Search: