I suppose while it has your attention, please vote for that feature https://connect.mozilla.org/t5/ideas/bring-back-pwa-progress...
I don't like the way web apps tie in with the pervasive tracking on the web, and the way they don't fit in well into the native UI and waste resources.
But it is indeed weird to remove the choice altogether.
One recent example, I pay for Spotify, but recently I started to pay for YouTube Premium to get rid of ads in the native mobile app, and it comes with YouTube Music.
I try YouTube Music and seems fine, was thinking to ditch Spotify and save that money, but YT Music do not have a desktop app like Spotify, on desktop is just trough https://music.youtube.com and has PWA features like "install", notifications and stuff.
I'm used to have that Spotify icon on my desktop and open the app, and being a Firefox user, with YT Music I can't have that experience, I can add a shortcut to my desktop, but it opens as a tab with all my other stuff opened. I don't like it. I guess I will stick with Spotify because of that.
In Chrome desktop, which supports PWA, you can install music.youtube.com, will add a desktop icon, opens in a individual window without tab/address bar etc. Is awesome. But is Chrome.
I'm considering use YT Music with Ungoogled Chromium to get the PWA features.
https://docs.microsoft.com/en-us/microsoft-edge/progressive-...
> That's the only reason I have Chrome installed, since I like to have different apps in different windows, and keep my browser tabs for websites.
I'd do the same thing, but Firefox is the browser I'd like to share data with. That's where my cookies, add-ons and user scripts live.
Throw in "when Web Assembly can interact with the DOM and browser APIs" and you have the most powerful cross-language, cross-platform UI toolkit in existence.
It'll mark the year of the Linux desktop... probably, maybe - please.
https://web.dev/learn/pwa/windows
- incredibly easy to setup (only a browser is needed) and use everywhere. Even management compatible.
- can be automated easily with ansible and/or docker
- remote pairing without a third-party cloud in between
- plug-ins just work even when being used remotely
- headless chrome can be proxied to the webview of vscode (a real browser running remotely in your browser)
Almost everything mentioned can be done with the tools you suggested BUT IMO it is not as smooth then just using vscode. This is coming from an arch (using arch BTW) / i3 guy.
If your objection is that it's inefficient and sometimes leads to bad quality output, I'd agree. But it's the option with the least friction so people gravitate towards it, we might as well make it work better.
IIRC that's actually possible on Linux, but a big pain and, like most command line switches, pretty undocumented.
But yeah, Firefox generally sucks for this use case and it's insane. It would be borderline trivial to implement, immensely useful and they've actually gone backwards on this type of stuff in many instances.
The browser is essentially an overlay operating system.
Kind of a crap one though.
Web assembly could be the basis for something that could break out of the browser.
Chrome: Menu -> More Tools -> Create Shortcut -> Check "Open as Window"
Edge: Menu -> Apps -> Install this site as an app
PWAs are my main use for Chromium.
It's absolutely the future, Firefox just isn't in that future.
> PWAs are my main use for Chromium
Mozilla already lost big when everyone decided to use Chromium for Electron-style apps and now they're actively running into losing big again.
Malicious apps will never trick users into granting access to folders they shouldn’t, whereupon they won’t have their files exfiltrated, encrypted, and held to ransom.