Yeah, you can use wasm on all platforms.
A ton of time and resources have been put into making web apps work across multiple rendering engines. These days, it can be difficult to have something break on one platform if you are using a modern development stack.…
Yes, much smaller install size and memory footprint. We have a comparison table on our readme: https://github.com/tauri-apps/tauri#comparison-between-tauri...
Assuming you meant Deno, we used Node for the CLI because most web devs already have npm installed. We want the getting started process to be as simple as possible. Our Node CLI is just a wrapper really, as nearly all…
If you scroll down to the roadmap, you can see that system trays are supported. We don't yet support native context menus, but that would be a relatively simple addition. Our GitHub readme has a table comparing…
Having the getting started button at the end is a good idea I think, we'll look into that. We say "web frontend" because that's as descriptive as we can be really. We support any web framework that runs in a browser. As…
It's actually inspired by the star system (https://en.wikipedia.org/wiki/T_Tauri_star).
The demo app has very basic styling, it isn't designed to be pretty. Since a Webview with HTML/CSS/JS is used for the GUI, you can style your app however you want.
Tauri's Bundler will automatically take care of shipping the Webview2 runtime, so there won't be any extra work required of you.
We didn't take over control, rather we helped setup an independent org around webview and other related repos. At the time, the original author of webview expressed plans to work on it a lot. However, this didn't really…
Servo is quite large and extremely difficult to build from source. We've tried to make it work with Tauri but decided it's not worth it, at least for now.
Yeah, you can use wasm on all platforms.
A ton of time and resources have been put into making web apps work across multiple rendering engines. These days, it can be difficult to have something break on one platform if you are using a modern development stack.…
Yes, much smaller install size and memory footprint. We have a comparison table on our readme: https://github.com/tauri-apps/tauri#comparison-between-tauri...
Assuming you meant Deno, we used Node for the CLI because most web devs already have npm installed. We want the getting started process to be as simple as possible. Our Node CLI is just a wrapper really, as nearly all…
If you scroll down to the roadmap, you can see that system trays are supported. We don't yet support native context menus, but that would be a relatively simple addition. Our GitHub readme has a table comparing…
Having the getting started button at the end is a good idea I think, we'll look into that. We say "web frontend" because that's as descriptive as we can be really. We support any web framework that runs in a browser. As…
It's actually inspired by the star system (https://en.wikipedia.org/wiki/T_Tauri_star).
The demo app has very basic styling, it isn't designed to be pretty. Since a Webview with HTML/CSS/JS is used for the GUI, you can style your app however you want.
Tauri's Bundler will automatically take care of shipping the Webview2 runtime, so there won't be any extra work required of you.
We didn't take over control, rather we helped setup an independent org around webview and other related repos. At the time, the original author of webview expressed plans to work on it a lot. However, this didn't really…
Servo is quite large and extremely difficult to build from source. We've tried to make it work with Tauri but decided it's not worth it, at least for now.