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

[flohofwoe]

Deno also just strips the type annotations when running TS code - at least by default. To get type checking you'll need to run via `deno run --check`, or use the separate `deno check` subcommand. No big deal since type checking and linting usually happens automatically in the IDE during development.

[bel8]

Good to know. Does it also preclude features like enums?

[bartlomieju]

Bartek from the Deno here. Nope, we do support enums OOTB.

[aabhay]

Tauri doesn't lock you in to one JS ecosystem. In fact, it doesn't require you to use javascript at all.

Also, we've had several developer framework startups get acquired -- Astro, Nuxt, UV, Bun, Vite. It doesn't exactly inspire confidence in a software that you want to last and give support for years.

[jpace121]

> Why would I use Tauri now?

You’re “backend” isn’t JavaScript.

[swiftcoder]

> and you get a reliable rendering engine

How is it more reliable than Tauri - aren't they both using the system webview?

[bel8]

Deno Desktop can bundle CEF (Chromium Embedded Framework) according to https://docs.deno.com/runtime/desktop/comparison

[fiatpandas]

Deno desktop can use system web view OR embed CEF. Tauri is just system web view.

[aabhay]

The benefit of Deno Desktop is it's like Tauri except for when you want it to be Electron???

[GeneralMaximus]

This is a feature many apps actually need.

E.g. Tauri uses WebKitGTK on Linux, which has historically been slow, unstable, and frequently lagging behind the main WebKit project. This is enough of an issue that even Tauri is working on the ability to use CEF instead of the system web view in Tauri apps.

Things are generally fine on recent versions of Windows and macOS. The system web views on these platforms will be evergreen versions of WebKit or Blink. But if you want to support very old versions of Windows or macOS, you might choose to use CEF instead of wrestling with Safari-from-five-years-ago.

[SpaghettiX]

But that would be the same argument for using electron? Why use this and not electron?