I don't have an opinion on Deno per se, but I quibble with this part of your point: > Code, specifically library code, which is what npm mostly consists of, in

I don't have an opinion on Deno per se, but I quibble with this part of your point: > Code, specifically library code, which is what npm mostly consists of, in its most ideal state should not have a never-ending variety. On the contrary, we do want to all arrive at one good way of doing a thing. This implies that there is in fact one good way to do most things, but in practice different people want different trade-offs and forcing them into a single codebase isn't possible when the options are mutually exclusive. You can't have a library that is simultaneously strict about types (panics if you pass a string instead of a number, say) and forgiving about types (automatically coerces strings to integers or vice versa).