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

181–190 of 418 posts

Re: Deno Desktop

#181

Post by oblio »

Abishek_Muthian wrote: post #145
oblio wrote: post #138

Earlier quoted context omitted.

> basic features like accessibility is missing but I'm sure it will be implemented soon. Accessibility implementations frequently are more complex than the entire UI drawing bits. Most custom UI toolkits never implement accessibility, even decades after creation. That hope is misplaced.

I agree about the complexity, but the core developers understand that the accessibility support is crucial and that's where my hope comes from. [1] https://github.com/zed-industries/zed/discussions/6576

That's good news, but I would continue the timer there. That issue is from March 2023 so the counter is at 3 years, 3 months. Let's see if they have anything decent before 10 years.

Re: Deno Desktop

#182

Post by bartlomieju »

LauraMedia wrote: post #93

Maybe it is because it is still in development, but building and running the Hello World example just gives me a blank terminal and a white window that is not responding.

Sorry to hear that, could I ask you to file an issue in our bug tracker?

Re: Deno Desktop

#184

Post by teaearlgraycold »

qbane wrote: post #153
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 doubt the benefit. Practically every Electron app on a desktop uses different versions of Chromium and many are very out of date because of the risk of breaking when upgrading.

People build web apps for an array of browsers and huge ranges of versions. I think if you started using some tech to deploy an end user program and knew from the beginning the browser could be updated beneath you it would work just fine. But if you start with a golden version of Chrome and put off updating for too long you’ve let yourself get too comfortable.

Re: Deno Desktop

#185

Post by bartlomieju »

pippoit wrote: post #100

can i open a socket with these tools ? can i open an odbc connection for example ? Or have i need to have a backend ? On desktop usually you can do much more than in the sandbox of a browser . I ask because i don't know these technologies. On windows, even if i don't like it, if the interface and the logic are not too complex, powershell with winform make you create things without "anything" installed and you can eas…

Yes, you can do all that. You get a fully-fledged Deno program that can do all of this, _plus_ you get a frontend GUI app.

Re: Deno Desktop

#186

Post by taffydavid »

kiicia wrote: post #119
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…

chromium is basically operating system at this point, it lacks kernel and ability to boot independently (added in chromium os), which is both good (from abilities standpoint) and bad (when copy of chromium is bundled with every app that renders webform with text field and button and nothing else) when it goes about using webapps as desktop apps, native PWA support should be used, it would - in theory at least - lesse…

Chrome OS is literally an operating system that's 90% through chromium

Re: Deno Desktop

#187

Post by bartlomieju »

numlock86 wrote: post #63

How does this differ from electrobun, which they explicitly mention, but make no point about? I had a quick drive with deno desktop and don't see how it's better. If anything it's lacking in comparison in my opinion. But hey, we can build desktop apps with deno now, too. So they got that going I guess ...

Bartek from Deno team hear. I'll love to hear what you feel is missing so we could improve `deno desktop` for more users.

Re: Deno Desktop

#188

Post by troupo »

teaearlgraycold wrote: post #184
qbane wrote: post #153

Earlier quoted context omitted.

I doubt the benefit. Practically every Electron app on a desktop uses different versions of Chromium and many are very out of date because of the risk of breaking when upgrading.

People build web apps for an array of browsers and huge ranges of versions. I think if you started using some tech to deploy an end user program and knew from the beginning the browser could be updated beneath you it would work just fine. But if you start with a golden version of Chrome and put off updating for too long you’ve let yourself get too comfortable.

> People build web apps for an array of browsers and huge ranges of versions.

en masse they don't. They just target the latest Chrome

Re: Deno Desktop

#190

Post by teaearlgraycold »

troupo wrote: post #188
teaearlgraycold wrote: post #184

Earlier quoted context omitted.

People build web apps for an array of browsers and huge ranges of versions. I think if you started using some tech to deploy an end user program and knew from the beginning the browser could be updated beneath you it would work just fine. But if you start with a golden version of Chrome and put off updating for too long you’ve let yourself get too comfortable.

> People build web apps for an array of browsers and huge ranges of versions. en masse they don't. They just target the latest Chrome

De facto they do because functionality built three years ago and tested then is running along side functionality they built yesterday and tested on today’s Chrome.

People also do seem to test on iOS Safari because that pain in my ass needs special care on my software. So if a site works on it they either got lucky or tested on an iPhone. It’s generally only other people’s weird tech demo stuff that doesn’t work.

Post reply on HN