Deno正式推出桌面应用框架
Deno团队今日发布了Deno Desktop——一个新的框架,允许开发者用JavaScript/TypeScript和Web技术构建跨平台桌面应用。这标志着Deno从运行时向全栈应用平台的战略扩展,直接挑战Electron和Tauri在桌面应用领域的主导地位。
技术架构与设计理念
Deno Desktop基于Deno的现代运行时,内置TypeScript支持、安全沙箱、Web标准API。与传统Electron方案不同,Deno Desktop不需要捆绑完整的Chromium,而是利用操作系统原生WebView(Windows上的WebView2、macOS上的WKWebView),显著减小应用体积。Deno的安全模型——默认无文件/网络/环境访问权限,需显式授权——也内建到桌面框架中,提升了应用安全性。
与Electron和Tauri的对比
Electron统治桌面应用开发多年,但体积臃肿(最小100MB+)和内存占用高的痛点始终未解决。Tauri通过Rust后端大幅缩减体积,但学习曲线较陡。Deno Desktop试图在两者之间找到最佳平衡:TypeScript/JS的全栈体验(像Electron),轻量级体积(接近Tauri),加上Deno的内置工具链(格式化、lint、测试)开箱即用。对于已经使用Deno的团队,这是零迁移成本的桌面方案。
社区反响：兴奋与务实
leleat: > Shared CEF runtime across apps. Every app currently bundles its own CEF copy. A managed shared runtime would drop binary sizes to a few MB per app. On the roadmap. This[0] sounds interesting. I am not familiar with CEF, so I wonder how the versioning works. When different apps require different versions of CEF, do we just essentially end up with the electron model where every app bundles their own browser (just slightly less bad). Or is there still an advantage to a “shared runtime” in that ca…
sheept: I was wondering how this integrates with Deno’s permission system, which is one of its biggest strengths especially for letting agents run amok on your device. The CLI reference page[0] notes, > The permissions you grant at compile time are baked into the compiled binary: I think it would be nice if this could be surfaced to the user somehow, like letting the user know and decide which permissions they want to give access to. [0]: https://docs.deno.com/runtime/reference/cli/desktop/#runtime…
bobajeff: I’m happy to see this I see that this provides CEF, Webview and Raw * backbends but it would be nice if there was also a launch in browser option (like WebUI has). To me that has the best tradeoffs if you want to avoid the mess that is webkitgtk but still not ship (and be in charge of updating) a chromium engine with your app. * https://docs.deno.com/runtime/desktop/backends/
40four: Deno continues to impress me. It’s honestly been quite a while since I started a new project without it. It has fully won my support over Node.js, the ecosystem has really matured nicely. I don’t know how often I’ll use this feature, but it’s really nice to have the option!
solarkraft: This is a smart thing to ship. For me it would totally be a consideration when deciding on a platform to use.
bel8: I’m happy for competition in this space, specially because Deno can run true TypeScript directly and not just strip types like the current Node implementation. With that said, this is going to eat a lot of Tauri market. Why would I use Tauri now? The 150mb of additional bundle size is just an extra 1 to 10 seconds of download time in most internet connections and you get a reliable rendering engine.
qudat: > Bindings are not IPC. The Deno runtime and the rendering backend run as threads / processes inside the same address space (CEF) or coordinated process group (WebView). Calls go through in-process channels, and the backend dispatches them from its run loop. — https://docs.deno.com/runtime/desktop/bindings/ I don’t understand how the coordinated process group works. Doesn’t that mean in this multi-process mode it must be IPC? Maybe the claim “shared memory space” is more an architectural descri…
doodlesdev: The overall feature seems really solid, but I’m impressed they couldn’t reduce the average package size further from 40MB even when not using CEF. I guess that wasn’t a huge focus when developing this feature? Tauri and Dioxus can easily hit less than 5MB for package sizes. I find the feature matrix comparison to be extremely well done and the sections beneath explaining advantages and disadvantages to be some of the best docs I’ve read recently. https://docs.deno.com/runtime/desktop/comparison/
HN社区反应热烈。很多开发者对Deno进入桌面领域感到兴奋,认为TypeScript原生的全栈桌面方案填补了市场空白。但也有务实的声音指出,桌面应用生态需要时间培育——Electron经过10年才积累起丰富的插件和最佳实践,Deno Desktop要追赶还有很长的路。
Deno的全栈野心
从Deno Deploy(边缘计算)、Deno KV(数据库)到现在的Deno Desktop,Deno正在从”Node.js替代品”转型为全栈应用平台。这次桌面框架的发布,让Deno覆盖了Web→边缘→桌面三大场景。对开发者而言,单一技术栈覆盖全平台是极具吸引力的愿景。但能否赢得企业级采用,取决于生态成熟度和长期维护承诺。
🔗 原文：Deno Desktop Documentation
💬 HN讨论：368条评论