18 comments

[ 2.6 ms ] story [ 53.1 ms ] thread
Every company I've ever worked for used Node.js. Almost none of them used it as a web server, however.

NPM is ubiquitous for frontend development, even when the backend uses a different technology.

Maybe better to have server side using deno. Deno can also publish to npm packages now. With its sec urity model, it maybe better for server side use.
Deno lost momentum. The teams that could have used Deno have adopted Go.
https://star-history.com/#denoland/deno

Seems alive to me.

I know GitHub stars are not the ideal metric, but Deno dying seems like an extraordinary claim that requires at least a little bit of evidence.

People don't unstar projects on github.

The metric to look for is the slope of that curve - how many new people get interested in deno each day? The slope of that curve is clearly trending downward.

From the chart, ∂{\star}/∂t remains pretty positive.
What's the typical curve for a project?

I would have thought it would be like other technology adoption curves - surprised if it _wasn't_ logarithmic

Losing momentum != (Not being alive || Dying)

Maybe it’s easier for you to understand the notation above.

Deno rocks. The integration is so high. There's just so many nonsense toolchain concerns in the rest of js that you don't have to worry about. Write TypeScript, run it.

The team is so laser focused on doing right for the users. They had a large customer complaining about LSP performance for a large project, & the team jumped on it & radically improved typescript LSP speed for large projects. That adaption & DX experience focus is so key. Great write-up, Deno 1.43: Improved Language Server performance, https://deno.com/blog/v1.43

I joined my current company a year ago. They use Nodejs in production web servers and data pipelines since their founding.

I wish they had not chosen this.

what are the problems you observed ?
(comment deleted)
I have to ask why is this article necessary ? Nobody is deleting nodejs anyway.
This feels like a chatgpt blog post, kind of about nothing.
Worse, it’s a kind of marketing piece to promote the business that wrote that blog post.
node.js is a decent piece of technology but you have to pick your packages very carefully. Even the popular packages suffer from bugs that make you wonder if any of those maintainers knows what they are doing.
Node is great, but I think we should collectively abandon npm:

It is centered around installing things as a user (in $HOME) as opposed to using proper packages.

The configuration format treats lines with `#` as not comments.

And, most importantly, security has been an afterthought.