Having to create shortcuts to load each profile or keep about:profiles open is frustrating compared to the Chrome experience.
It's not enough to stop me using FF as my daily driver, but it is enough to stop my partner using it for theirs.
681–690 of 850 posts
Having to create shortcuts to load each profile or keep about:profiles open is frustrating compared to the Chrome experience.
It's not enough to stop me using FF as my daily driver, but it is enough to stop my partner using it for theirs.
Either I just don't go to them, or I have really good luck, because none of the sites I visit are "broken."
Earlier quoted context omitted.
Your point is that struggling publishers will stay relevant, gain subscribers and afloat/make more money by implementing ad blockers, worst user experience and safety checks to make their sites less accessible. I'm sure it'll happen any day now.
Absolutely, yes. They will be empowered by tools they don't yet have to make it feasible to slowly "boil the frog". Remote attestation is just such a tool.
I switched back to firefox last year and haven't looked back. I still use chrome on another laptop sometimes, the performance difference from my human perspective is literally zero. These days, it's much more common for me to encounter a website that works in firefox but not chrome than the other way around. I actually switched for good when I had to use firefox to file my taxes, because the IRS free self-file site w…
Firefox out of the box indeed does not cause broken websites. However, the demographic of this forum probably will use Firefox with "Multi-Account Containers", "Temporary Containers", "uBlock Origin", and a few more. These are amazing for privacy and productivity, but will occasionally cause broken websites. Source: I am a Firefox-first user who occasionally uses plugin-less Chrome because the aforementioned plugins…
This, again, can be restated as incompetent developers cause broken websites (!)
("... do not attribute to bad faith that which can be explained by stupidity")
If you keep feeding the Google monster you soon won't be able to browse the internet without a 3rd party attesting that your computer is worth browsing that site. https://arstechnica.com/gadgets/2023/07/googles-web-integrit...
Earlier quoted context omitted.
> Which sites require those? How would that allow them to make more profit? Practically every banking site (or more importantly banking apps). And a lot of weird cases like bus/train timings app, mobile operator apps, etc. You don't see that a lot with websites yet because the web isn't so severely constrained as mobile apps are. But the moment they appear, it will go the other way. One good example of this is AMP -…
Making a website less accessible doesn't make any sense. You've given an example of apps like before and you've yet to substantiate any points you made, maybe bank logins have a reason to be secure but that forum you go to doesn't, and wouldn't do this. If they wanted to make it less accessible they could easily do that by forcing you to use newer browser versions which some boilerplate sites with frameworks do, from…
Website operators don't need to outright block you, they can just start putting certain features behind "the wall".
Earlier quoted context omitted.
Gecko is the browser engine. WebRender is a component of Gecko, specifically a GPU-based 2D rendering engine. It is not a browser engine.
Yes, WebRender makes up the compositor portion of the browser rendering engine. A very large, critical portion of it. Thus, saying "Gecko had a good and honorable run" is disingenuous to the large-scale changes and progress the developers have made (and continue to make) on the rendering engine.
I simply think that it's time has come. Remember that Mozilla itself once intended to replace Gecko with Servo.
I have no doubt that WebRender is brilliant, but WebRender will not save Gecko, and Gecko will not save Firefox.
If Firefox is worth saving — and I think that with hard choices, its decline can be reversed — then Gecko and its components are non-differentiating ballast that must be dropped if the balloon is to get over the mountain. IMHO, of course.
Earlier quoted context omitted.
When these sites break I prefer to spam their support or just not use them. If they won't support firefox then they don't deserve my patronage.
It's not patronage if you don't pay. Google would rather not have you as a user if it costs them any amount of time to support you. The relationship here is adversarial on both sides and pretending otherwise doesn't help anyone.