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

171–180 of 418 posts

Re: Deno Desktop

#171

Post by chmod775 »

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...

When the new client was built, microservices were the hot new buzzword.

The new client is some weird plugins/services based architecture. Things that'd barely warrant their own class in a boring OOP-based UI framework are instead now "isolated" services. The reality of this isolation being that if one piece breaks, the whole UI becomes unusable anyways. Dozens of things that in another app would've been just a simple synchronous call now behave like remote procedure calls and messages, forcing all the complexity of distributed systems into a local application for no reason.

That's why it runs like ass, breaks if you look at it wrong, and your CPU draws more power when using the client than when playing the game at 200FPS.

Re: Deno Desktop

#172

Post by divan »

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…

This. It's nuts how the whole industry accepts that typesetting engine from 80s with bunch of hacks on top is currently dominating cross-platform UI development.

Re: Deno Desktop

#173

Post by nottorp »

Hmm suppose you have a node GUI-less application. What would you pack it in to have something reasonably self contained to deploy?

Re: Deno Desktop

#174

Post by Klonoar »

jorisw wrote: post #120
m-schuetz wrote: post #92

Earlier quoted context omitted.

> They consistently miss the mark in adopting UI patterns from their host OS. What you suggest is a disadvantage is one of the key advantages of Electron to me. I precisely do not want my things to look different on different OS. I don't have the resources to test my apps on all devices, and knowing that whatever I test on one system looks the same on another is A+.

That's an advantage to you. Not necessarily to your users.

Users don't actually give a shit.

This is a techie complaint, and that's opting for a charitably nice description.

Re: Deno Desktop

#175

Post by ivell »

tonyedgecombe wrote: post #89
mfru wrote: post #72

Earlier quoted context omitted.

At this point I think that would be a more sane outcome than whatever it is we have right now.

We were writing and shipping desktop applications with it back in the nineties. Although many of the arguments against it were similar to the arguments against Electron today.

I think the UI look and feel was very ugly for many users and that caused its demise. The cross platform skin was ugly. The native skins were in the uncanny valley.

The framework was reasonably good for its time. By the time good looking UI frameworks came, the bad reputation was already set.

Re: Deno Desktop

#176

Post by TylerE »

Levitating wrote: post #157
Culonavirus wrote: post #71

Earlier quoted context omitted.

That is not why people use Electron. The goal is not and never was to just be a "UI toolkit" and "adopting UI patterns from their host OS". Chromium has so much stuff packed into it, its insane. All that utility comes with Electron. And that's a good thing. If you ever worked with video, for example, you know that having the full power of a modern browser in a desktop app is a game changer. Video playback (not to men…

gstreamer is not that complicated

It has a really really crappy security record, though.

Re: Deno Desktop

#179

Post by bartlomieju »

bel8 wrote: post #95
flohofwoe wrote: post #58

Earlier quoted context omitted.

Deno also just strips the type annotations when running TS code - at least by default. To get type checking you'll need to run via `deno run --check`, or use the separate `deno check` subcommand. No big deal since type checking and linting usually happens automatically in the IDE during development.

Good to know. Does it also preclude features like enums?

Bartek from the Deno here. Nope, we do support enums OOTB.

Re: Deno Desktop

#180

Post by bartlomieju »

krawcu wrote: post #54

Why did they describe electrobun as macOS only? I checked their docs and it has support for Windows, macOS and Linux https://docs.deno.com/runtime/desktop/comparison/ https://github.com/blackboardsh/electrobun#platform-support

Thanks, I'll update the docs. When we wrote them a couple weeks back, Electrobun was announcing Linux only support.
Post reply on HN