Neat!
Is there any "bundle/integrate with existing native application" story like Tauris sidecar [0]?
Deno Desktop
251–260 of 418 posts
Re: Deno Desktop
#252Is it going to support iOS/Android?
The docs say it's planned but no proper roadmap for it yet.
Re: Deno Desktop
#253Earlier quoted context omitted.
I agree and disagree, you can't target everything, but most (not shit) devs will target at least Safari - 1 or 2, simply because the iPhone market is too good to miss out on. And Safari being, well, Safari, means targeting that is a pretty safe bet for anything else.
Depends on the region, no one where I work has an iPhone or a current Mac, so stuff gets tested on FF and Chrome, and Safari gets thoughts and prayers. We would test on Safari if it were simple, but alas.
Skipping testing on 15% of all devices to save $600? Sounds like a poor business decision.
Re: Deno Desktop
#254I swear we're just going to end up with Java again.
[dead]
Re: Deno Desktop
#255I watched traditional GUIs for a while and used many of them, mostly via ruby as wrapper, sometimes also via java. I finally reached the conclusion not too long ago, that web-apps are the only real alternatives now. Too many things do not work when it comes to traditional desktop applications. There are even regressions, e. g. ruby-gtk4 barely works for me. And there is no real support for any problems really. People…
> I'd wish we would have a real "write once, run everywhere"...
Hi! I'm trying my best okay? Hokusai Pocket might currently be composed of wood and string, but one day he will be a real boy!
Re: Deno Desktop
#256> 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...
CEF is + has been the de-facto standard when you have a native app and want to do a web UI.
It's not the only option, but it's the most mature with the largest amount of docs + stack overflow questions, so it's a "safe" choice.
If you peek into the native resources files of most games/desktop apps, you'll find a good portion of them bundle + use the CEF dll.
Re: Deno Desktop
#257Earlier quoted context omitted.
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.
> Users don't actually give a shit.
Have you ever had a job as a tech support? If not, you don’t have anything to say.
People do complain about inconsistent UX. Especially when it does not behave like the platform it’s on.
Re: Deno Desktop
#258> 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…
[deleted]
Re: Deno Desktop
#259Earlier quoted context omitted.
I think the fact that you listed off five toolkits for three different OSes, all of which are "that OS's own toolkit," might point at the root of the problem here.
Windows is so fucking old that I think it has a right to try again. And, btw, the reason Microsoft even bothered is because (dun dun dunnnn) lots of internal apps at Microsoft were written with Qt, not MFC, and leadership got pissed when they realized (they couldn't tell the difference, since Qt does the native++ technique). As for Linux, yeah, thats a shitshow. Qt was closed source, Linux isn't, so they made Gtk, bu…
Gtk is hardware (GPU) accelerated, while Qt Widgets is software/CPU-rendered.
Re: Deno Desktop
#260Great, another way to make shipping bloated javascript apps easier. Just what we need.