[jsxlite]

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.

[jauntywundrkind]

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

[mr90210]

Deno lost momentum. The teams that could have used Deno have adopted Go.

[fallingsquirrel]

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.

[josephg]

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.

[Equiet]

Comparing to Node it seems to be at about the same rate: https://star-history.com/#denoland/deno&nodejs/node&Date. It's actually quite impressive how close it is.

[ikesau]

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

[nine_k]

From the chart, ∂{\star}/∂t remains pretty positive.

[mr90210]

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

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