Zero-native – Build native desktop apps with web UI
zero-native.dev
Zero-native – Build native desktop apps with web UI
1–10 of 65 posts
Re: Zero-native – Build native desktop apps with web UI
#2> No borrow checker. No lifetimes. No fighting the compiler for 20 minutes over a string.
I don’t like this attitude, both zig and rust have their strengths.
Re: Zero-native – Build native desktop apps with web UI
#3Im not sure if people are getting the biggest problem in electron desktop apps.
Its RAM usage not the disk!!
Why are they all making the same thing in different ways?! I have never worked on an electron app where the executable size was an impediment to the business. Its always the RAM/CPU usage. If we are going to work on the same webviews like electron and others, how will this make any difference?
Re: Zero-native – Build native desktop apps with web UI
#4I love the redefinition of "native desktop app" - a web app which uses the system web-view instead of bundling Chrome.
Re: Zero-native – Build native desktop apps with web UI
#5> Use the system WebView for lightweight apps, or bundle Chromium via CEF
so basically a vibe coded Tauri in zig? I don't like calling webview dependent applications "native desktop apps".
Native desktop apps means using the OS primitives and directives to draw the UI imo; WinForms, SwiftUI, and their ilk.
Re: Zero-native – Build native desktop apps with web UI
#6Im not sure if people are getting the biggest problem in electron desktop apps. Its RAM usage not the disk!! Why are they all making the same thing in different ways?! I have never worked on an electron app where the executable size was an impediment to the business. Its always the RAM/CPU usage. If we are going to work on the same webviews like electron and others, how will this make any difference?
Cause they all share one webview. Electron apps each run their own version of chromium
Re: Zero-native – Build native desktop apps with web UI
#7Im not sure if people are getting the biggest problem in electron desktop apps. Its RAM usage not the disk!! Why are they all making the same thing in different ways?! I have never worked on an electron app where the executable size was an impediment to the business. Its always the RAM/CPU usage. If we are going to work on the same webviews like electron and others, how will this make any difference?
Using the system webview theoretically saves memory. Though it's still not great.
Re: Zero-native – Build native desktop apps with web UI
#8> No borrow checker. No lifetimes. No fighting the compiler for 20 minutes over a string. I don’t like this attitude, both zig and rust have their strengths.
Rust has bad ergonomics. You will see that "attitude" as long as coding exists, or lifetimes are fixed in a way to allow you to omit them in contexts which are not concurrent or are embarrassingly parallelizable.
Re: Zero-native – Build native desktop apps with web UI
#9Given this is from Vercel and most likely vibe coded (hopefully not), I wonder how many zero-day vulnerabilities will be there... :^)
Re: Zero-native – Build native desktop apps with web UI
#10No screenshot examples even? :/