just reflecting.Async-by-default, single-threaded core, Where Node shines, where it hurts, and what you’d pick for a greenfield project now ?
Comments
nullfield•2w ago
Generalized, noting there are always exceptions: many CS lessons seem to be needing repetition among Node.js users, in the general sense and where CS wasn’t really taught.
Mistake? Gah. Probably in a lot of cases. The ecosystem around it is both “robust” in the sense of projects and libraries, and “objectively awful” for permitting some of the recent security issues seen.
ECMAScript was never intended for where it’s at now, and all the lipstick Google applies won’t change that, even if it “works fast” “now”.
What I’d pick for a new project? It depends, tell me about the project. …it probably won’t be Node.js though.
burntoutgray•2w ago
I use Bun or Deno for my projects. Always disliked Node.js and especially npm.
Ryan Dahl created Deno to address his regrets regarding Node.js shortcomings, limitations.
nullfield•2w ago
Mistake? Gah. Probably in a lot of cases. The ecosystem around it is both “robust” in the sense of projects and libraries, and “objectively awful” for permitting some of the recent security issues seen.
ECMAScript was never intended for where it’s at now, and all the lipstick Google applies won’t change that, even if it “works fast” “now”.
What I’d pick for a new project? It depends, tell me about the project. …it probably won’t be Node.js though.