Deno Desktop
21–30 of 418 posts
Re: Deno Desktop
#22I was wondering how this integrates with Deno's permission system, which is one of its biggest strengths especially for letting agents run amok on your device. The CLI reference page[0] notes, > The permissions you grant at compile time are baked into the compiled binary: I think it would be nice if this could be surfaced to the user somehow, like letting the user know and decide which permissions they want to give a…
> Runtime permissions for desktop apps (a permission prompt on every filesystem / network access, i.e. Deno's permission system applied to desktop sandboxing).
Re: Deno Desktop
#23Interesting but IMHO as we see on mobile providing WebViews work. Maybe instead of having Electron, Tauri, Electrobun, now Deno desktop but also plenty of alternatives then desktop browsers should provide WebViews on desktop with sandbox and permissions that make those applications usable. The alternatives listed here would just be fallback for a transition period until the WebViews are "good enough".
Re: Deno Desktop
#24I wonder if it supports opening invisible browser windows and doing things like intercepting cookies. In my desktop application I leverage a hidden browser window to manage auth state and use it like a proxy for the rest of the application. Might try to port it to deno desktop.
Re: Deno Desktop
#25Re: Deno Desktop
#26With 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.
Re: Deno Desktop
#27Re: Deno Desktop
#28Earlier quoted context omitted.
Consistency is a large factor in any good design, UI design more so.
They have internal consistency. The iOS version looks like the macos version which looks like the web version, etc. This upsets HN users but the rest of the world decided that apps looking like windows built ins doesn't matter.