- cross-posted to:
- firefox@lemmy.world
- technology@lemmy.world
- cross-posted to:
- firefox@lemmy.world
- technology@lemmy.world
You must log in or register to comment.
Similarly, Rubino says web apps in Firefox will not use a minimal browser frame and will continue to show a main toolbar with address bar, extensions, bookmarks
But why, the whole purpose is to behave like a stand alone app.
Man, they really fuck up everything they touch now.
What the …? Then why do it on the first place. Mozilla being stupid again.
I mean there’s a solid chance not a single coder now is the same as back when it was removed? It’s been quite a while. 😅
A) Because they suffer from some kind of weird delusion that they will some day gain mote than single digit market share and then subsequently lose it because somebody hacked your grandmother‘s computer with a YouTube video that was running in full screen?
B) They are the worlds laziest coders and google paid them 20M a year to do nothing for… however many years it’s been.
I wouldn’t say they’re lazy. Quite the opposite in fact. They’re just so under-resourced compared to Chrome, which has the benefit of a massive for-profit company backing it, in addition to a much larger range of third-party contributors (from Edge, Brave, Vivaldi, Opera, and more). They struggle to keep up with the fast pace at which web standards evolve.
They are the worlds laziest coders and google paid them 20M a year to do nothing for…
Only a fraction of a fraction of this is actually used in relation to the browser, and only a fraction of this goes to the actual coders/developers.
I am sure the devs do the best work they can do and are allowed to do. This is entirely a management issue.
On desktop I think that’s less valuable, and personally, I like the confidence of knowing that eg uBO still works, and the predictability of how it will behave.
The Connect thread is interesting; PWAs are a nebulous term and everyone has different use cases for them, so if this allows to cover some of those with significantly less investment, that makes sense to me.
Yeah when they removed it there was virtually no comment on it. At the time everybody understood PWAs were just… you might as well use a new window and press F11. It’s just window dressing.
I mean I get it, there’s some marginal use cases. Sure. And it looks pretty in the end. But I also get why from a dev perspective there’s just very little actual point to them.
Because it’s low effort.
Less time and money spent on useless features like progressive web apps means more time can be spent on useful features like data harvesting, AI bullshit, and Facebook-approved advertising.
PWAs are not a useless feature. It’s an incredibly useful and powerful set of web standards that allows sites to provide excellent user experiences more akin to what apps could provide, without users needing to go and download an app—which a lot of users, especially more privacy and security focused users—hate being asked to do.
Whole point is to give the aesthetics of a standalone app… Ridiculous executive slop.
… after removing them and ignoring them for several years.
About time.
If only they could allow extensions to work with iPhones.
afaik, they really can’t. IIRC apple only allows webkit browsers on the platform, so that alone rules out any and all extensions made for firefox. Firefox on iphones is essentially reskinned safari - and that’s about it.
At least this is what internet has led me to believe, dunno, not an apple user.
That’s not true anymore, you can use a custom engine now
TIL, has it been long when the restriction was dropped? At least wikipedia claims that firefox is webkit on ios, so possibly that is still the case?
Pretty sure you’re right but idk if they’ve updated it to use their own engine yet. They’d probably have to rewrite the app, or large parts of it, and that takes time. Maybe someone who uses Firefox on iOS could tell us.
I think it’s allowed only in the EU? And there’s absolutely no way Mozilla has the resources to support a Safari-based iOS app in addition to a Gecko-based one, on top of everything else they do.
Ah, did not know that it was on Apple’s side. Still hoping they will allow it (or being forced to - like with sideloading).
Is that up to them though? Aren’t browsers on iPhones only allowed to be wrappers around the built in safari engine? If that’s still true extensions that interact with the web page it’s self would probably be pretty limited.
