It takes courage to use npm as a product. The inability of its leader, Isaac Schlueter, to communicate the reasoning behind decisions pose a risk as a choice for long term toolchain.

My company will move to yarn for now and jump ship to Deno as soon as it reaches all of my check marks.

What are your reasons to not moving to Deno right away? What check mark is left?

@c3r38r170 ngl main thing is getting enough brain juice to actually pick through deno.land/x.

A few example check marks for a library to be picked into my production stack:

1. Battle tested
2. Large and active user base
3. Responsible contributors
4. Comfortable API
5. Serverless friendly
6. Multithread/clustering awareness by design

@c3r38r170 bonus point is to absolutely kills in at least one of the metrics. e.g. the concurrency of actix web

I just want to move away from JavaScript forever. Typescript can only do so much to polish that turd.
I'm still keeping an eye out for blazor and similar stuff.

@ars1 It's an inevitable convergence because the dominant client env is the web, thus js. server side is kinda forced.

Following this direction, the next small thing must be Deno since it sticks better with the web api.

The next big thing should be WASM so you may start moving away from js/ts, but this is counting in decades.