Live data from Hacker News

Deno Desktop

docs.deno.com

271–280 of 418 posts

Re: Deno Desktop

#271
post #251

Neat! Is there any "bundle/integrate with existing native application" story like Tauris sidecar [0]? [0]: https://v2.tauri.app/develop/sidecar/

From what I understood, what you want is `deno desktop --include […]`. > Includes an additional module or file/directory in the compiled executable.

This works well. I’ve been using it to bundle other binaries with my applications and so far my users have had no issues on Windows, Linux, and macOS. I’m still a bit surprised given how new it is

Re: Deno Desktop

#272
post #117

Earlier quoted context omitted.

Great for the developer. The user doesn’t use Mac, Windows and Linux. Just one for work and one at home, with mostly different apps, so they couldn’t care less if it looks the same on different platforms.

They may care, however, if they get anything at all. I do not have the resources to target something to all platforms, so the alternative wouldn't be "Users get UI targeted towards their OS", the alternative would be "Users get nothing since developers don't have the time to also target their system".

> I do not have the resources to target something to all platforms

What resources is actually needed? More often than not it just requires good engineering. You do not have to duplicate everything across platforms.

Re: Deno Desktop

#273
post #270
post #26

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.

> Deno can run true TypeScript directly and not just strip types What exactly do you mean by that? Because no js engine carries the ts types into the runtime as far as I know. Deno and nodejs both use v8 as the runtime. v8's internal types are not connected at all to the ts types regardless of the wrapper. The only difference might be when/if static type checking is performed.

I think they mean deno handles transpiling for you so there’s no visible machinery for this aspect of the program. It’s just convenient.

Re: Deno Desktop

#274
post #266
post #261

Earlier quoted context omitted.

The one which OS has to offer. Web is bad everywhere outside of the browser.

I want to have both linux and mac users (but maybe also android, ios, windows). You clearly see the issue.

> You clearly see the issue

I don’t. VLC is available everywhere, so your requirement is clearly not a problem. Jetbrains is available on all major desktop OS.

Re: Deno Desktop

#275
post #26

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.

Temporarily at a place with 10-15 mbps. 150 MB is around 1 minute.

I grew up on 30 mbps. >= 100 is all I need nowadays.

But 10 mbps and websites and downloads really start to take a while.

The more bits and bytes you save, the more people will be pleased with your stuff! Even if they don’t know what bits and bytes are, and just go based on impatience

Re: Deno Desktop

#276

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/

> I'm happy to see this I see that this provides CEF, Webview and Raw

They beat Tauri at their CEF support.

Webviews are a mistake in most cases. They're too platform-specific, and certain Webviews (Safari/Webkit) are buggy as hell, making platform support a nightmare. (Linux, ironically, is even worse due to how underbaked webviews are on the major desktop Linuces - Tauri is barely functional on Linux.)

Deno Desktop could be a real contender in this space. It's good to see more Electron alternatives.

Re: Deno Desktop

#277

Earlier quoted context omitted.

With Dioxus, program logic compiles to native code instead of running it through a JS engine, and it ships its own HTML renderer (Blitz) instead of bundling a whole browser. So it's a lot more lightweight and performant than Electron. As a minor bonus, the live-reload is also faster than what frameworks like React do. It truly has subsecond latency, which isn't exactly a game changer but is nice when iterating on vis…

Sounds similar to Wails. It does the same but with Go instead of Rust.

I don't think so, wails is more like tauri rather than diouxus

Re: Deno Desktop

#278
post #26

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.

>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.

this is misleading. there is no "running true ts". you will always be running pure js (until someone actually develops a "true" ts engine), and deno does "type stripping" just the same. the only difference is that it bundles the tools and makes it transparent and config-free which is more convenient (although more rigid).

Re: Deno Desktop

#280

Earlier quoted context omitted.

From what I understood, what you want is `deno desktop --include […]`. > Includes an additional module or file/directory in the compiled executable.

This works well. I’ve been using it to bundle other binaries with my applications and so far my users have had no issues on Windows, Linux, and macOS. I’m still a bit surprised given how new it is

That's great to know, thanks! Will look into that.
Post reply on HN