3 ms·

CRUD is literally what node.js is built for - lightweight APIs that then have to do some slow operation async against a store - which they overlap requests acro

• Lazare 8y ago
  I'm honestly unsure if your post is sarcastic or serious.
  • abraae 8y ago
    Ha, I have the same feeling, even after several re-reads.
• benatkin 8y ago
  Yes, and it doesn't have a big enough advantage for it to be picked up. Usually developer productivity and memory use (node doesn't cause memory leaks but it doesn't prevent them either) is more of a limiting factor than the execution model. Node has found plenty of use outside of what it was originally built for (the canonical examples are web servers). As far as I can tell, it's used more widely and critically as a tool for packaging client-side scripts or for client-side applications (vscode, electron, Slack). Examples of places where it seems like node would be an obvious choice, but it's not: blogs (WordPress still reigns), Mozilla's Add-ons (runs on Django [1]), Slack (very heavy user of JS on the front end, but backend is coded in PHP [1]), Zapier [2] (Python backend, though custom integrations are often written in JavaScript) 1: https://github.com/mozilla/addons-server https://github.com/mozilla/addons-server 2: https://slack.engineering/taking-php-seriously-cf7a60065329?gi=c414f3d4bb41 https://slack.engineering/taking-php-seriously-cf7a60065329?... 3: https://zapier.com/engineering/automating-billions-of-tasks/ https://zapier.com/engineering/automating-billions-of-tasks/