r/Deno • • May 15 '25

Deno may become a new standard in the AI-driven era

0 Upvotes

Hi everyone – this is my first post in r/deno.
I'm a backend engineer based in South Korea, and I’ve been closely following the intersection of AI and software development. I’d like to share a thought that I believe may become more relevant as AI becomes more deeply integrated into our workflows.

As AI systems increasingly take the lead in writing and managing code, we’re seeing a shift in what makes a development platform “effective.”
What was once optimized for human developers may now pose unnecessary complexity for AI agents.

In this context, Deno appears to offer an architecture that aligns well with the needs of AI-driven development:

  • A secure-by-default, sandboxed runtime

  • URL-based module imports with no reliance on central registries

  • Native TypeScript support out of the box

  • Built-in tools for formatting, linting, and testing

  • Clean support for WASI and edge environments

These features align with what AI systems tend to prefer: simplicity, predictability, and minimal configuration.
As autonomous agents become more capable of handling tasks end-to-end, the need for deterministic and low-friction environments will likely increase.

Of course, no platform is universally ideal.
For instance, Python—despite being the dominant language in AI—often struggles with dependency hell, environment mismatches, and packaging complexity. These are real barriers when AI agents try to run or ship code independently.

In contrast, Deno’s integrated and modern design could offer a cleaner, more consistent foundation for such scenarios.

Just wanted to share these thoughts and hear what others here think.
Do you see Deno gaining traction as the development world becomes more AI-centric?


r/Deno • • Nov 01 '24

Why typescript if everything runs on javascript?

1 Upvotes

I have recently learnt the basics of typescript and I want to switch to it, however I have a doubt.

Can someone explain how it works on the frontend and backend?

As far as I have got to know, in both frontend and backend we are required to compile / transpile Typescript to JavaScript to run it, which would produce so many files that are uploaded on a server, isn't that very heavy?

Or am I wrong and Typescript can run at least on backend without first becoming javascript somewhere along the way.

Also not clear what would be the difference between compiling and transpiling and why don't we do just one.

And I know how to use typescript and javascript, I have made projects in javascript and now thinking of changing the base language for one of them to ts as I like it more because I am aware of all its benefits


r/Deno • • 8d ago

Why Deno’s Future Feels Stalled—and the Case for "OpenDeno" (A Multi-Engine, Truly Embeddable Architecture)

0 Upvotes

Many of us share a growing anxiety about Deno's trajectory. What began as a bold, clean reboot of the server-side JavaScript ecosystem has increasingly felt constrained. Between shifting priorities, growing complexity around Node compatibility, and the sheer overhead of maintaining a monolithic runtime, developers are rightly asking: Where is Deno headed?

The problem is not Deno’s vision. Capability-based permissions (--allow-net, --allow-read), first-class TypeScript, and strict adherence to Web standards remain the single best blueprint for modern JavaScript runtime security.

The real bottleneck is architectural: Deno's security model is held hostage by its implementation. By coupling itself deeply to V8 internals (C++ handles, Fast API Calls, and V8 heap snapshots) inside a monolithic CLI, Deno locked its brilliant ideas inside a single, heavyweight silo.

It doesn't have to be this way. To turn Deno's core insights into an enduring, ubiquitous standard, we need to decouple the specification from the engine: OpenDeno.


The Vision: Decoupling Specification from Implementation

OpenDeno is a multi-engine, highly embeddable runtime architecture built in Rust. Instead of treating V8 as an immutable foundation, OpenDeno treats JavaScript engines as swappable backends behind a unified, capability-based security layer.

1. Engine-Agnostic Core (opendeno-core)

At the center sits a pure Rust abstraction layer containing:

  • The Permission Engine: Declarative enforcement of file, network, and environment boundaries completely independent of any JS runtime.

  • Standard Web APIs: Engine-neutral implementations of standard specifications (fetch, crypto, URL, Streams, TextEncoder).

  • Engine Trait: A lean interface for script evaluation, value conversion, and lifecycle management.

2. Pluggable Engine Adapters

Rather than chasing nanosecond micro-benchmarks at the cost of massive binary size, OpenDeno provides targeted adapter crates:

  • JavaScriptCore (JSC) Backend (opendeno-jsc): Perfect for macOS and strict iOS environments where custom JIT generation is restricted, delivering battery-friendly native performance.

  • QuickJS / Boa Backend (opendeno-quickjs / opendeno-boa): Sub-megabyte memory footprints, instant cold starts, and zero C++ toolchain headaches. This unlocks secure TypeScript scripting on Android, constrained edge gateways, and IoT micro-nodes where V8 cannot physically run.

  • V8 Backend (opendeno-v8): Retained for raw, high-throughput server-side compute where memory consumption is a secondary concern.

3. A Standardized, Cross-Engine Native Plugin ABI (opendeno-ffi)

Historically, native plugins have been fractured whenever underlying JS engines change.

OpenDeno standardizes a stable, engine-neutral C-ABI crate. A native plugin (.so / .dll) interacts strictly with an abstract OpenDenoAPI table rather than raw engine internals.

  • Build a native Rust, C, or Go/Hike plugin once.

  • Run it without recompilation across any OpenDeno-supported backend—whether the host is executing on QuickJS on a Raspberry Pi or JSC on Apple Silicon.

  • Because host embedding and plugin extension share identical value-marshaling needs, the same minimal FFI crate powers both application embedding and third-party native addons.

4. Embeddable by Default: Bulletproof In-App & Embedded Browser Security

Deno chose to be a standalone CLI tool competing directly with Node.js and Bun. OpenDeno flips the priority: embeddability first, CLI second.

By shipping a clean C-ABI and Rust API, host applications gain an unprecedented level of execution safety:

  • Embedded Browsers & WebViews: Today’s desktop applications, hybrid UIs, and game clients frequently embed WebViews or custom rendering engines. However, standard browser scripting offers an all-or-nothing security model—either full browser sandbox restrictions or dangerous native bridge vulnerabilities (as seen in Electron's history). Embedding Deno's capability model into these environments guarantees a vastly more secure in-app browser runtime. Developers can expose granular, hardware-bound capabilities (e.g., allow read access only to an asset cache folder, restrict network calls strictly to application endpoints) without opening arbitrary OS attack vectors.

  • Enterprise Host Runtimes: Enterprise hosts can safely execute multi-tenant user scripts directly inside JVM applications (via Project Panama / JNI) and .NET Core services (via P/Invoke) with hard, declarative permission boundaries and zero heavy process-spawning overhead.


Moving Beyond the CLI Wars

Trying to beat Node.js by playing Node's game (chasing npm compatibility and monolithic CLI bundling) is a race to the bottom.

Deno gave the world the correct paradigm for safe, modern JavaScript execution. OpenDeno is the architectural step required to liberate that paradigm from V8, transforming Deno from an opinionated command-line tool into a universal, multi-platform standard.

Would you prefer seeing Deno evolve into a swappable, embeddable standard like this, or do you believe doubling down on V8 and Node compatibility is still the right path?


r/Deno • • Jan 07 '23

I Don't Like JSX

0 Upvotes

Is there a way I can stay away from JSX and still do all the cool and useful things?


r/Deno • • Nov 13 '25

GenesisTrace v1.0.0 is here! 🦅💻😶‍🌫️🥼💻🤔

Post image
0 Upvotes

Be sure to checkout https://jsr.io/@pedromdominguez/genesis-trace for a full list of examples! #ZeroDependencies


r/Deno • • May 02 '25

Deno's Decline (6 Regions and Falling)

Thumbnail dbushell.com
0 Upvotes

r/Deno • • Dec 08 '24

Hey Deno, time to take the lead. Make Node.js be compatible with Deno: "sandboxing may or may not be implemented" is vague, not specificity, wishy-washy

Thumbnail
gitlab.com
3 Upvotes

r/Deno • • Oct 14 '24

What are the target demographics for Deno's "Programming should be simple" production/advertisement?

0 Upvotes

What are the target demographics for Deno's Programming should be simple production/advertisement?

I'm curious who management decided they are trying to reach, specifically, with that production/advertisement?

I'm also curious how much that production/advertisement cost?

For the specific target demographic part, I'm wondering how Deno management intends to measure the success or failure, or break-even point for the investment in that advertisement/production?


r/Deno • • Jun 17 '20

Setting up deno.land using Visual Studio Code

0 Upvotes

r/Deno • • Jun 15 '22

I wish the manual had plain Javascript examples

0 Upvotes

I think it would be beneficial to the growth of deno if the manual contained Javascript examples as well as Typescript examples.

I even think this would be useful for Typescript people as a kind of easy-read version of code. Let’s face it, Typescript contains more information than Javascript.

I think this would be true even for very simple examples:

function handler(req: Request): Response { 
  return new Response("Hello, World!"); 
}

Is easier to read without the types:

function handler(req) { 
  return new Response("Hello, World!"); 
}

I know it’s not that big of a deal if you know Typescript, but the thing is, a lot of people coming to deno don’t know Typescript. Having plain Javascript there would be good. Maybe a tabbed interface?

Here’s some very advanced visualization technology:


r/Deno • • Jul 04 '22

Hey guys, any tell me how cool this video is

Thumbnail
youtu.be
0 Upvotes

r/Deno • • Jul 22 '22

its fresh better than nextjs

1 Upvotes

hi guys im using nextjs and graphql for to build web app,now i was thinking to learn fresh with deno to build website so fast im main with less time

how u suggest for me ?


r/Deno • • 10d ago

I really love Deno, but…

5 Upvotes

Deno has always been my go-to tool for everything I do. Over the past year, all my local agents have used Deno instead of Python for scripts and other tasks. But lately, Deno’s features have become so unpredictable…I’m still using Deno, but how long can I keep using it?


r/Deno • • Oct 10 '20

DENO_ A GAMECHANGER OR AN ALTERNATIVE? -Node.js beginners guide to deno

3 Upvotes

r/Deno • • 1d ago

I measured npm loading on Deno 2.9.7 against Node and Bun on the same installed tree

0 Upvotes

I maintain CompatLab. I wanted to separate “Deno can load this npm entry” from “my app will work after a migration.” We fixed the package list before running the study. Deno 2.9.7 passed root import for all 97 executable versions in the sample and root require for all 96 with an applicable entry. The other three frozen rows contained declarations or a platform binary. Node.js 24.21.0 and 26.10.0 and Bun 1.4.2 returned the same root counts.

The subpath result was more instructive: [email protected] loaded at the root, but import("yargs/browser") failed on all four profiles. A rebuild from the retained npm lock reproduced those failures. This was a browser entry on offline server runtimes, and Deno’s diagnostic changed between runs. I’m leaving the cause of that Deno discrepancy open.

We used the same sealed node_modules for all runtimes, ignored lifecycle scripts, and gave Deno -A inside the network-disabled gVisor boundary. The tests evaluate modules on Linux amd64/glibc. They leave application behavior, Deno Deploy, and upstream test suites open. Study and downloadable results

If you’re deciding whether to move a real Node dependency to Deno, I’d like to see where this evidence helps or falls short. A public package name, exact version, import path, and target Deno version are enough to start. You can reply here or use the short volunteer task. Please skip private code and full lockfiles.

AI helped draft this post. The linked data includes the report and replay.


r/Deno • • Jul 31 '21

generate a restapi for sql?

0 Upvotes

Are there any frameworks to generate an API from an sqlite db to do the grunt work or do I have to write out every endpoint by hand?


r/Deno • • Apr 23 '23

Framework for Angular

0 Upvotes

Hey there,

new to Deno, new to TS. I saw Fresh is considered an official framework for deno according to the page and seems to be widely adaopted. However, from my understanding it is a fullstack framework. So I was looking into alternatives.. Found oak.. Which is by far less popular according got github and not an official framework for deno.

As I will need to work with much more people for the frontend, as I am more at the backend site, I aim to use Angular for the Frontend.

Anyone using Angular and Angular in their stack for enterprise software? My main critics are: Secure and well maintained Compatible with Angular Typescript (so express/nodejs are kinda of the table for me) best case official for deno

In case you wonder why angular? Well maintained and backed by google (a lot of trust the project will be around for long time) fully fledged framework typescript

why typescript? better to maintain harder to produce poor code

resource for comparison are hard to find.

Thanks in advanced folks!


r/Deno • • Aug 12 '24

How to add uWebSockets.js ?

0 Upvotes

r/Deno • • Jan 01 '24

Why continuing using Deno rather than learning Rust?

0 Upvotes

When I started my journey, I needed to add a lot functionalities to my little js script. So I need to learn ts. Since I didn't need to work with any Node app, using Deno was not a problem for me. I'm satisfied.

Now I need to deploy it to a webapp. Armed with more knowledge on computer science and software engineering, I wonder if there is any advantage for me to continue using Deno (with Fresh?) rather than using Rust from scratch? Here are the reasons for me to choose Rust:

  • The switch cost for me is small

  • My toolkit is richer

  • I can join into another ecosystem

  • It can compile to WebAssembly

  • Deno is written in Rust

  • I can have more chance to broaden my knowledge and open my mind

  • Another language to put in CV

I don't really have any reason to continue using Deno, except the convenience of continuing using TS. Is there any thing that I miss? Like, if you still use TS with Deno, then what makes you not make the switch?


r/Deno • • Oct 09 '22

how do you uninstall deno

5 Upvotes

r/Deno • • Dec 17 '24

Minimal wasi_snapshot_preview1, without preopens or filesystem read/write intended, for Deno, Node.js, Bun

Thumbnail
gitlab.com
0 Upvotes

r/Deno • • Nov 20 '25

Just updated Genesis Trace! v1.0.4 if officially out!

Thumbnail
gallery
1 Upvotes

Publishing the http framework, heartbeat monitor, and DRUMROLL Genesis ABI to unify the JavaScript ecosystem soon as well!


r/Deno • • Jun 22 '20

5 reasons why Deno will stop using TypeScript

Thumbnail
startfunction.com
0 Upvotes

r/Deno • • Feb 10 '21

Deno needs to stop forcing import extension.

0 Upvotes

VS code doesn't allow importing of modules if you specify extension .ts but deno won't bundle/compile without importing .ts extension.

Deno is contradicting VS code and making development messy. At least specify an option so we can bundle/compile typescript files without specifying import extensions.