Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno Desktop

docs.deno.com

Post reply on HN
Print view View original

341–350 of 418 posts

Re: Deno Desktop

#341

Post by moogly »

synchrone wrote: post #299
echelon wrote: post #282

Earlier quoted context omitted.

The biggest weakness of a framework like Tauri is the choice to target system webviews instead of bundling a browser runtime. It seems great to be able to cut hundreds of megabytes out of your app installer, but the platform differences wind up being a complete and ongoing pain in the ass. Tauri support on Windows is phenomenal. Tauri on Mac runs into lots of WebKit/Safari issues, especially on older Mac machines tha…

Regular Tauri app (aptakube) user on linux here: the experience is very adequate and smooth, I have no complaints. Speed benefits relative to Electron (similar app: K8S Lens) alone are enough to deal with many possible issues. Could be attributed to app developers going the extra mile, but I suspect it's the framework choice.

Targeting and building Tauri apps for Wayland, specifically, is a massive headache due to assorted webkitgtk bundling/incompatibility madness.

Re: Deno Desktop

#342

Post by gf000 »

pjmlp wrote: post #323
gf000 wrote: post #266

Earlier quoted context omitted.

I want to have both linux and mac users (but maybe also android, ios, windows). You clearly see the issue.

When I started programming, one had to repeat in Assembly the same application for each computer brand. We are not that bad nowadays, it is a skill issue. There are plenty of ways to have portable applications with native UIs without shipping a browser. Somehow we managed to do it for decades and without AI writing the code for us. If you want to ship a browser, I already have one, thus standard Web, with a daemon if…

I agree on the standard web point, but you still failed to reply to what is a native UI for every OS.

Portable frameworks exist, but they are at most native to a single platform.

Re: Deno Desktop

#343

Post by socalgal2 »

NekkoDroid wrote: post #334
Lucasoato wrote: post #163

Earlier quoted context omitted.

Just to let you know, CEF was used for Riot and League of Legends client as well [0]. The results haven't been nice, but I'm not aware if this was a problem with the CEF technology itself or other component/processes are to be blamed. [0]: https://www.riotgames.com/en/news/architecture-league-client...

Both Steam and Battle.net use CEF for their UI as well. And IMO they are on 2 ends of the "nice to use" from the implementation side (Steam being a sluggish hell and B.net being nice). Though then again B.net is only for Blizzard games, so they can also optimise for the limited set games.

> Steam being a sluggish hell

news to me. Been using steam since it launched. Never noticed it being sluggish

Re: Deno Desktop

#344

Post by syrusakbary »

asim wrote: post #131
flexagoon wrote: post #113

Earlier quoted context omitted.

Why "etc."? Isn't it just node, bun and deno? Genuine question

In case someone is using something we haven't heard of e.g some are running using cloudflare workers which also has some unique runtime properties. AWS has something called LLRT. https://github.com/awslabs/llrt https://developers.cloudflare.com/workers/runtime-apis/

We have created Edge.js that can run Node.js apps fully using your preferred JS runtime: V8 or QuickJS.

https://edgejs.org/

Re: Deno Desktop

#345

Post by MoonWalk »

rjrjrjrj wrote: post #300
raincole wrote: post #98

Earlier quoted context omitted.

> UI patterns from their host OS I genuinely wonder who ever want that, and what apps those people use on their PC. Can you imagine, for example, Blender Foundation says that their next goal is to make Blender's UI look more like the host OS?

I have used Blender just a bit, but it was very jarring when I first opened it and discovered that it has its own menu bar within the window, rather than at the top of the screen. It has its own save/open window rather than using the system-provided one, as nearly all truly native Mac apps do. I doubt most Mac users like this. I have somewhat more experience with QGIS. It has a standard Mac menu bar, but the icons ar…

So... it has a menu bar where it belongs: on the application's main frame. But yes, that'll be jarring for Mac users, who have suffered a single menu with split-personality disorder for far too long.

As for the common dialogs, I agree with you. There's no better example of why you should stick with common dialogs than the shitshow that is Microsoft Office. The file-save... thing is mind-bogglingly bad. It looks like a hastily-thrown-together debug screen. You have no idea what you're looking at. The fields are primitive, unnecessarily-huge box outlines. There's no treeview to show you where you're working in the filesystem. There's a big list of what, history? Why?

Garbage.

Re: Deno Desktop

#346

Post by iancarroll »

kodablah wrote: post #315
leleat wrote: post #66

> Shared CEF runtime across apps. Every app currently bundles its own CEF copy. A managed shared runtime would drop binary sizes to a few MB per app. On the roadmap. This[0] sounds interesting. I am not familiar with CEF, so I wonder how the versioning works. When different apps require different versions of CEF, do we just essentially end up with the electron model where every app bundles their own browser (just sli…

I used CEF for a project and Google is detecting CEF via some opaque algorithms and not allowing logins from it. From https://security.googleblog.com/2019/04/better-protection-ag... : > Because we can’t differentiate between a legitimate sign in and a MITM attack on these platforms, we will be blocking sign-ins from embedded browser frameworks starting in June Granted this was years ago, maybe the situation improved?…

Most apps (on desktop or mobile) open third party auth flows inside the user's default browser, which makes this a non-issue. For one, if you embed the Google login flow into your app then I can't reuse my existing session in my browser. But it also exposes my full credentials to your app for no reason, which is a good thing to avoid.

Re: Deno Desktop

#347

Post by poisonborz »

lillesvin wrote: post #6

As much as I like cross-platform stuff, I also really like native UIs that follow native UX patterns, etc.

This ship has long, long sailed. If you don't spend your all your 24 hours as an office worker using Microsoft software, or you're locked in with a PC from 30 years ago, chances are almost every single UI you use will look differently, besides some microscopic agreements, like back button or a burger menu.

We just got used to it. There is some very vague thin layer of "commonly accepted patterns and symbols", but otherwise users just get through it.

Re: Deno Desktop

#348

Post by TylerE »

socalgal2 wrote: post #343
NekkoDroid wrote: post #334

Earlier quoted context omitted.

Both Steam and Battle.net use CEF for their UI as well. And IMO they are on 2 ends of the "nice to use" from the implementation side (Steam being a sluggish hell and B.net being nice). Though then again B.net is only for Blizzard games, so they can also optimise for the limited set games.

> Steam being a sluggish hell news to me. Been using steam since it launched. Never noticed it being sluggish

You haven't? Steam has been a miserable experience for years. Great way to make a monster gaming rig replicate the eMachines 1998 experience.

Re: Deno Desktop

#349

Post by loaph »

conradludgate wrote: post #15
jorisw wrote: post #3

> Web technology is the most widely-known UI toolkit in the world. Poor choice of words there IMHO. The reason Electron apps get a lot of flak is because they are everything _but_ a UI toolkit. They consistently miss the mark in adopting UI patterns from their host OS. Web tech is just web tech. Yes it will allow you to render a button, but even unstyled, the button won't necessarily look native to the OS, and will v…

How is it a poor choice of words? It might not be "native" UI, but they never claimed as such. I've always felt that native UI on Linux always looks incredibly ugly and I'd much rather use a nicely styled HTML+CSS layout instead. In my experience, Electron mostly gets flak for being bloated and slow, it not being native is sometimes a secondary point people add on top. I've always wanted to build a direct-browser int…

This isn't exactly what you were suggesting, but it made me think of https://hacks.mozilla.org/2026/02/making-webassembly-a-first... since that article is about not needing to go through js to use wasm.

Re: Deno Desktop

#350

Post by atombender »

Lucasoato wrote: post #163
leleat wrote: post #66

> Shared CEF runtime across apps. Every app currently bundles its own CEF copy. A managed shared runtime would drop binary sizes to a few MB per app. On the roadmap. This[0] sounds interesting. I am not familiar with CEF, so I wonder how the versioning works. When different apps require different versions of CEF, do we just essentially end up with the electron model where every app bundles their own browser (just sli…

Just to let you know, CEF was used for Riot and League of Legends client as well [0]. The results haven't been nice, but I'm not aware if this was a problem with the CEF technology itself or other component/processes are to be blamed. [0]: https://www.riotgames.com/en/news/architecture-league-client...

Also Spotify. I believe Spotify was one of the earliest adopters of CEF, maybe the first major adopter?

The desktop app was originally a native C++ app, but they switched to CEF around 2011-2012. (It caused a very noticeable drop in performance!)

Post reply on HN