Hacker News new | ask | show | jobs
by bearjaws 6 days ago
I cannot use a browser that is owned by a company who's financial model is dependent upon browsers being nerfed.

Apple and Google have far too many incentives to wall garden browsers, Apple due to the app store, Google due to advertising.

Independent browsers are the only safe path forward.

4 comments

Funny, I prefer to use Safari because it is just a damn web browser and isn't trying to let every webslop dev try and re-invent the wheel in slow JITed Javascript and build their own crappy operating system. Whatever their reason, Apple is the enemy of my enemy, and therefore, in this regard, my friend.
Well this preview includes many changes made to WebKit which Kagi, a so called independent browser, depends on. It's good news for you.
You're correct. Which makes it all the more inscrutable that the Firefox team doesn't embrace PWA's as a differentiator.
What did they nerf
Apple: adblocking, PWA being put in a odd spot, surely to be followed by a post "nobody was using it" before being removed, if they mention it at all.

Google: ad blocking

Ad blocking isn't nerfed
It is when compared to Firefox. Safari and now Google claim that it's for security, as the newer interfaces expose way less attack surface for malicious add-ons. I think that it's true that it does improve security, although I'm not sure that I believe Google when they say they're not doing it to stop people from blocking their main revenue source.
At least the blocker I use, uBlock Lite, isn't nerfed. It doesn't have Manifest v3-ish limitations, and can do dynamic blocking, injection, etc.
It cannot do dynamic filtering [1]. Another big one I forgot about is no CNAME uncloaking. Don't get me wrong, uBOL is still a great add on, it's just not possible to do everything you could with the manifest v2 version.

[1] https://github.com/uBlockOrigin/uBOL-home/wiki/Frequently-as...

uBO Lite is exactly MV3, it has most of MV3 limitations plus its own limitations comparing to Chromium. Safari just auto converts MV3 codes to Safari's own blocking engines.
PWA for starters? They are not interested in Indie devs anyways. Might as well let us use PWA no?
PWAs enjoy excellent support in Safari:

https://pwascore.com

Safari arguably has better PWA support than Firefox last time I checked.
How
Nothing. This is just FUD.