Node.js

“the vast majority of daily Microsoft Defender offenders I have to wade through... are related to Node being used in various Microsoft applications”

“I find Node's documentation to be some of the worst for never being able to answer the specific question I have”

“spent its time actually shipping stability while everyone else was chasing the next shiny runtime hype cycle”

“Nodejs wasn't easier for people. JS is a horrible language where simple stuff like comparisons, array access, and member access are broken.”

“nodejs natively supports a huge set of typescript with built-in type stripping these days”

“in Node.js, which gave birth to npm, you can now do many stuff without external dependencies”

“It's stable, has a good (and growing) standard library and has enough backing to be self sustaining.”

“node succeeded, because it managed to transplant the validated engineering and mindshare of js devs to the backend”

“NodeJS itself qualifies as boring, but the entire ecosystem around it is still a mess.”

“It is more about being a dynamic language where V8 can only help as much, thus C++ addons, rewrites into .NET, Java, Go, Rust”

“Yes, sometimes you have to ship node.js or a whole web browser, but the tooling for that is slightly less insane than the analogous tooling for python.”

“although node@24 can directly run typescript file, but stripe the types, without type-checking”

“You could just go back to Node where they aren't engaging in a modern day Ship of Theseus every other week.”

“How many more examples of malware postinstall scripts do we need before Node quits running them by default, without warning?”

“trying to maintain a pretty large body of TypeScript code in a runtime-agnostic way (including even Node, since 24.2)”

“Node includes SQLite and Argon2 at least, if the issue is the interface then that is easily fixed.”

“Node is JavaScript, and those awesome server-side geniuses dump too-easy tooling while recreating every problem of every stack ever”

“I love the simplicity of Node.js that each process or child process can have its own CPU core”

“I honestly can't think of a single practical scenario where I'd pick Deno over Node + npm today.”

“Every Electron app ships with its own copy of Chromium (for rendering the UI) and Node.js (for system APIs).”

“In node.js I've seen time and time again some slow task that happens only every now and then, but which causes significant latency spikes.”

“It's very satisfying to rent a 250MB memory machine and let it process GB's of data using streams.”

“Bad language, ecosystem full of buggy unmaintained packages with the worse security profile of all the common languages”

“recent versions of Node.js which can strip TypeScript types I don't even need a build step”

“The only limitation I run into using Node natively is you need to do import types as type imports”

“with its "running environments" (Chrome, Node, etc.), has done what Java was supposed to do in the 90s”

“the node.js packaging ecosystem wouldn't have committed so many own-goals if it'd been designed by people with more historical awareness”

“NodeJS is also needed because most Docker files that use Rust in our organization also have NodeJS in them”

“Both bun and node do type stripping of ts types, and can compile a cli to a single file executable”

“Worker threads can't handle I/O, so a single process Node.js app will still have the connection limit much lower”

“spinning up multiple NodeJS instances and putting an nginx server in front to do load balancing”

“As a developer I can build web and media applications that you couldn't ever imagine building 20 years ago.”

“My long-term bet on Node being "boring" and "stable" continues to pay major dividends.”

“You can go very far with just node alone (accepts typescript without tsc, has testing framework,...)”

“Node itself is still fine and you can do a lot these days without needing tons of library.”

“I chose the Node example because I feel like it offers the same "ease-of-use" that draws people to Python”

“The Javascript ecosystem however (nodejs, npm, yarn etc) are what take away from an otherwise excellent programming language.”

“Moving from Python to Node for per-process fully-fleshed out async and share-nothing concurrency however is perfectly sane.”

“Node literally exists to do one thing and one thing only really well: async programming.”

“The point is that Node was forced into this model by V8 limitations, then sold it as an advantage”