aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornetop://ウィビ <paul@webb.page>2026-10-11 12:39:26 -0700
committernetop://ウィビ <paul@webb.page>2026-10-11 12:39:26 -0700
commit2349bd8b8c6723b763a4dd2aac20e99298680a6e (patch)
treeddca031401bef7935f024c158f8afb23248eea2f
parent7dc788714e4e1f62a0400423f12e0a6ae5eec995 (diff)
downloadblog-2349bd8b8c6723b763a4dd2aac20e99298680a6e.tar.gz
blog-2349bd8b8c6723b763a4dd2aac20e99298680a6e.zip
new memo
-rw-r--r--memos/WM-105.txt129
-rw-r--r--version.txt2
2 files changed, 130 insertions, 1 deletions
diff --git a/memos/WM-105.txt b/memos/WM-105.txt
new file mode 100644
index 0000000..6a9e969
--- /dev/null
+++ b/memos/WM-105.txt
@@ -0,0 +1,129 @@
+
+
+
+
+
+
+
+Document: WM-105 P. Webb
+Category: Tooling 2026-10-11
+
+ Beginning of the Ende
+
+Abstract
+
+ The trend of VC-backed tooling ending in abandonment rears its ugly
+ head again. But hey, people gotta eat, right? The community will pick
+ up the slack and steward the projects, right?
+
+Body
+
+ Deno is dead.
+
+ Announced[1] on a Friday[2], of course, the team has fled to
+ Cloudflare and in a year, will stop working on the runtime. Kudos to
+ them for finding an exit, Womp womp to us.
+
+ This is the second time in just as many years that a technology I
+ depend on is “given up to the community.” If you’re new here, Disc[3]
+ came about because the team behind Gel fled to Vercel and gave their
+ project up to the community. This was two years ago and as of this
+ writing, no updates have been made on the “blessed” fork[4] of it.
+
+ (Perhaps a bit petty of me to point out but someone in the Gel
+ Discord has been rather hostile/cowardly about my efforts and thus I
+ find delight in proving assholes wrong)
+
+ The frustration of the Deno community is palpable and has created the
+ best crashout[5] I’ve seen in some time:
+
+ > What the fuck do you mean Deno is ending development in a year????
+ >
+ > I JUST learned how to use this stupid runtime.
+ >
+ > I don't give a fuck about your Cloudflare acquisition or your edge
+ > computing or whatever the fuck a Durable Object is.
+ >
+ > I JUST WANT TO RUN MY TYPESCRIPT FILES.
+ >
+ > Why is there a shutdown date????
+ >
+ > WHERE IS THE FUCKING DOWNLOAD BUTTON FOR MORE YEARS OF SUPPORT????
+ >
+ > I went to the releases page and there is no deno-forever.exe.
+ >
+ > WHY IS THERE NO deno-forever.exe?????
+ >
+ > Just compile another 10 years of development into a fucking
+ > executable and give it to me.
+ >
+ > I don't want to learn Node.js again.
+ >
+ > I don't want to migrate to Bun.
+ >
+ > I don't want to understand your business model.
+ >
+ > I JUST WANT MY DINOSAUR BACK.
+ >
+ > You cannot just Deno.exit(0) an entire runtime.
+ >
+ > STUPID FUCKING CLOUD NERDS.
+
+ Ryan Dahl’s comment[6] on HackerNews gave me pause (emphasis mine):
+
+ > It's a joint decision and I agree with it. I'm most invested in its
+ > success and have put the most work into it - and I no longer think
+ > it's where I can do the most important work. **There are some**
+ > **good ideas in Deno and it's well engineered - but it ultimately**
+ > **is not solving big problems. It has been sucked into the**
+ > **gravity well of node compatibility, which forces it to behave**
+ > **exactly as Node does. Why reimplement Node? It works. Marginal**
+ > **performance or UX or security benefits are not enough.**
+ >
+ > …
+ >
+ > We'll ship monthly releases for a year, and Deno stays
+ > MIT-licensed. If people want to carry it forward, I'd like that.
+
+ My brother in Christ. YOU reimplemented Node and now you’re bored? I
+ get it was done for adoption purposes but like, that’s a solvable
+ problem? Whatever, this ain’t my first rodeo[7].
+
+ There’s bound to be other forks but this one’s mine; I’m calling it,
+ Ende (“end” in German). “Ende” is an anagram of “Deno” which is an
+ anagram of “Node” and it’ll do things differently:
+
+ — no more Node compatibility
+ — no more distractions, period; that means Deploy, KV, Jupyter, &c
+ are also getting the boot
+
+ The roadmap? Per-module permissions, sandboxes for untrusted code,
+ post-quantum crypto in Web Crypto, better binary output, &c. I depend
+ on Deno for all of my APIs and personal projects, and now am building
+ a serious business on it; EOL[8].
+
+ 📸[EOL Program][IMG1]
+
+ I’m aiming for a soft launch in December so I can work out production
+ kinks before a proper one. It’s gonna be quite the flex when Ende
+ development is happening on EOL. Anyhoo, placeholder site for Ende[9]
+ is up, subscribe to the mailing list if you want to be notified when
+ it’s “official” (proper marketing and documentation websites). EOL
+ also has a mailing list[8] if you want to know when the beta opens.
+
+ I am very busy but excited. I wanted to build the Neue Internet[10]
+ after all, looks like I’m getting my chance. 🕸️
+
+References
+
+ [1] <https://deno.com/blog/cloudflare>
+ [2] <https://blog.cloudflare.com/deno-joins-cloudflare>
+ [3] <https://disc.sh>
+ [4] <https://github.com/gelstable/gel>
+ [5] <https://github.com/denoland/deno/issues/37004>
+ [6] <https://news.ycombinator.com/item?id=50023277>
+ [7] </WM-095>
+ [8] <https://eol.sh>
+ [9] <https://ende.sh>
+ [10] </WM-078>
+ [IMG1] <https://cdn.webb.page/blog/2026/wm-105-a.JPG>
diff --git a/version.txt b/version.txt
index 2bad8e2..32453e0 100644
--- a/version.txt
+++ b/version.txt
@@ -1 +1 @@
-2026.09.28 \ No newline at end of file
+2026.10.11 \ No newline at end of file