- They originally bet on being a TypeScript dialect that didn't quite match the expectations of node in a few small places that ended up mattering hugely.

- One of the original value propositions was "deno compile" and "deno bundle", and those never actually worked well enough to be robust for our real-world use cases (early on they didn't support TLA, then dynamic imports didn't work, then they had issues with ARM compilation)

- Then they simultaneously tried to support node syntax out of the box with npm import specifiers _and_ create a new javascript registry (jsr.io)

- At the point where we expected them to actually make their base-level ecosystem robust, they pivoted to edge compute, and then the writing was on the wall

The one silver lining here is that Deno had already increased their node/npm compatibility. Migrating off of the jsr ecosystem and back to npm is going to be less painful than one might imagine. I expect present LLMs to be sufficiently good at the task, for example.

I've been waiting for a literal decade for this, for the same reasons as the grand-parent poster. I literally had a chapter of my NSF CAREER proposal on this (failed, woof, but the reviewers were wrong! this rocks). The potential here is absurd. Eg, novel query optimizers and novel DB indexes could be created that, when connected to the right charting tools, would automatically emit efficient graphics and query results. Very, very cool work, thank you.

Have you heard "have you played guitar for 20 years, or have you played guitar 20 times for a year?" Time only helps with accumulating wisdom if you let it.

It's not particularly helpful; you could easily have done the 5 minutes of work.

I prescribe 20 hours of KSP to everyone involved, that'll set them right.

RMarkdown isn't going anywhere! Quarto exists to bring the RMarkdown experience that folks love to a broader set of users and contexts. It is true that we try to keep the .qmd experience in Quarto pretty close to the .rmd experience in RMarkdown, and it is true that Quarto does things that RMarkdown never will. But it's not the case that "RMarkdown is being phased out and replaced with Quarto".

If you want the serious version of the idea instead of the LLM diarrhea, just go Jonathan Shewchuk’s robust predicates work: https://people.eecs.berkeley.edu/~jrs/papers/robustr.pdf from 1997.

- there's competition, and so if it's possible to rent for less than 1000-eps and still profit, someone will

- there's no competition, which is a cartel, the kind of thing that civilized societies ought to frown upon