Why do so many projects fail to include any screenshots at all?
Maybe the authors don't think it's necessary, but step 3 under `Getting Started` is called `Creating UI`. Why would they not show what the result of the tutorial looks like?
> Ship updates to your users that are tiny
What about the users that are medium or large?
So this aspires to be something like Tauri, but with Zig for the fast/native bits, and leaning harder on and more opinionated about the frontend/UI part?
That's a pretty interesting proposal, but also a staggeringly huge amount of work.
Bold choice: https://electrobun.dev/docs/guides/Compatability#:~:text=No%... (that text appears right next to "macOS (arm)")
Given that, I was curious how their workflows folder looked but, well, that answers that question: https://github.com/blackboardsh/electrobun/tree/9ce4ed636100...
I'm a fan of more frameworks for desktop apps that wrap system webview rather than embedding Chromium.
Chromium is awesome and all, but it's just way overkill for many apps, and doesn't make sense for the download size and the need to support auto-update for security features.
>Security and Performance with isolation between the main and webview processes
That's one of the performance characteristics I'm afraid will hinder certain applications.
It sounds like you need to use a IPC bridge to share data between the main process and renderor. Which means copying all the shared data. Like if I wanted to use ffmpeg for decoding video then each frame I'm waiting for a the decoded image to be copied before rendering it.
How do they manage the OS-specific stuff with pure TypeScript? How does it compare in benchmarks against Tauri for size and speed?
"...and cross-platform desktop applications" the homepage says
But, Sadly, this is mac only[0] no windows or linux ? Do I understand it correctly ?
[0] https://electrobun.dev/docs/guides/Compatability