Deno has a very cool architecture where almost all of the standard library is imported from outside of the runtime. Which means you can pin specific versions of

Deno has a very cool architecture where almost all of the standard library is imported from outside of the runtime. Which means you can pin specific versions of unstable APIs, and never get caught by surprise even as they're being iterated on rapidly. They also say in the post that eg., the deno.json file changes are backward-compatible As far as I know, Deno 1.x runtime upgrades are always backwards-compatible