They're now in our documentation to make them easier to find. There's a whole collection of annotated examples on how use Deno. Take them as-is or use them as a reference when you're developing.
I have some bittersweet news -- I decided to leave Deno. Going to be joining a really cool company, continuing to work in Rust.
Deno was a great place to work, full of really smart folks. I got to work on some great projects: rewriting the HTTP server to nearly 2x throughput, some major refactoring of the event loop and timers to make them an order of magnitude faster, working on rebuilding the V8 -> Rust interface to make it as fast as humanly possible...
... while also improving the developer experience with better errors.
Too many fun projects to count!
I still think #Deno is the best choice for server-side JS and #typescript, robust command-line tools and many other places. It's so much better than everything else.
Looking forward to announcing the new role in the near future and continuing to work in the high-performance #Rust arena. 🚀
Blog Post: I wrote about my struggles trying to open up outgoing net requests in a safe way for #Dropserver apps using #Deno's permissions. It didn't go well 😭
Offer a low-code solution and your users want more customization? Here are 3 kinds of "escape hatches" you can add to your product:
🧩️custom data transformer
🧩️custom external HTTP connector
🧩️custom chart or UI component
I've been thinking about restarting work on #Tapir. Development stopped because I hit a wall with the database system. Writing Tapir in #Deno was a long sequence of yak-shaving without much payoff; most of my dev time was spent implementing JSON-LD, Web Signatures, and a database layer that should have been a library if Deno had better Node compatibility at the time.
#Fedify's tutorial, which previously assumed you were using #Deno, can now be followed using #Node.js and #Bun! (What is Fedify? It's an ActivityPub server framework.)
However, they are written for Fedify 0.8.0, which hasn't been released yet. You can test it with the pre-release version, 0.8.0-dev.164, though.
🚀 Much faster language server
🐢 Key improvements in node:worker_threads and node:vm
💾 Snappy startups with V8 code caching
☁️ New "deno serve" subcommand
🚨 Updates regarding Deno 2
Slack chose #Deno to build its next generation platform because:
✅ native TypeScript & web standard APIs support
✅ secure-by-default,👍for enterprise apps
✅ can be compiled into a portable, self-executable binary
In the past, I’ve really wanted to try out other search engines: Mojeek, Kagi, Ecosia; but there was one thing that made me stay with DuckDuckGo — the Bangs. Well, not any more!
interro is a shim for your search engine that enables DDG Bangs, but better! Instead of routing your requests via DDG, it loads all Bangs into memory and handles redirects locally. You can use any search engine as fallback.
Netlify built their Edge Functions with #Deno Subhosting over AWS Lambda because:
⭐️ global availability without config
⭐️ autoscale without pre-provisioning
⭐️ lower cold starts
⭐️ simple, robust APIs that supports web standards
Our LSP is now nearly 2x faster, especially when working in large projects. Here's a benchmark of editing and navigating files in a 24mb project in milliseconds.