> What’s next for Deno?

Who cares? Why does the world need so many fringe tools/runtimes? So much fragmentation. Why does every project have to be a long-term success? Put some stuff out if its misery. Don't waste the time of the already few open-source contributors who pour hours into something for no good reason.

▲

steve_adams_86 5 hours ago | parent | next [-]

Deno is much more than a fringe tool. It's a genuine improvement in many ways.

▲

MuffinFlavored 4 hours ago | parent [-]

The world doesn't need a dozen JS runtimes.

The world doesn't need a dozen JS engines.

The world doesn't need many dozens of Linux distros.

The world doesn't need a handful of BSD distros.

The world doesn't need many dozens of package managers.

The world doesn't need hundreds of JS frameworks.

The world doesn't need dozens of programming languages or chat protocols or CI/CD systems.

The world doesn't need dozens of init systems, service managers, display servers, audio stacks, universal app formats, build tools/bundlers.

Deno may have dragged the JS runtime space forward, fully agree. Maybe it served its purpose and it is time to say goodbye.

	▲	steve_adams_86 3 hours ago \| parent \| next [-]
		If Deno moved things forward, doesn't that suggest that we do need efforts like this to support ongoing progress? There doesn't seem to be strong evidence to the contrary in the JS ecosystem.
	▲	balamatom 2 hours ago \| parent \| prev [-]
		The world doesn't need so many people or anything they have to offer it.

▲

balamatom 2 hours ago | parent | prev [-]

I'd argue that the mainstream, lowest-common-denominator tools are the ones which waste people's time. (Especially when they're backed by an incumbent. Deno, on the other hand, clicked immediately.)