Hacker News new | ask | show | jobs
by killyp 2686 days ago
Firefox my dude. Has plugin support (uBlock) on mobile.
3 comments

Quite, Any browser that doesn't use chromium is the correct choice. Monopolies are bad, and it's hilarious that people are celebrating one of the demise of one most destructive monopolies of the computing age with "just use $new_monpololistic_product, it will be different this time"
A lot of the same people decrying the Chrome monopoly never the less push for more and more bloat in the web standard, thus helping to enforce that monopoly by ensuring that hardly anyone has the resources to make a reasonable competitor.
Time to deprecate the web and start from scratch.
Doing so today would only result in a worse and more proprietary product, I suspect.
More proprietary than "basically Google just tells everyone how it's going to be"? Maybe. It'd be hard to make it worse though. What people seem to really want out of the web is a VM platform and a document layout engine, so why not design a new VM that is intended first and foremost to be an efficient application platform, and then make one of those applications an open source document layout engine? You don't have to be married to HTTP and all its woes either. You could even port a current "legacy" browser to it. And if that document layout engine is found to be lacking, we can make a new one without breaking everything because its just another application on the VM.

Hell, you could compile the VM with an HTML5/JS target and get forward compatibility too.

A worse standard is unlikely to win people over. Even a better standard is unlikely to win.

Take HTML, JavaScript, and CSS, remove 90% of the cruft. Now, include what people want like a much better table element that by default can handle Adaptive screen sizes etc etc.

Chromium and Firefox are open source so you can probably get support in them by writing the code yourself. But, good luck gaining traction.

You'll have a really very bad time deciding what is cruft on those.
No, but "click to play" for javascript would be a good start.
At least Webkit/Blink are open source and have multiple implementations. With that in mind, how do we distinguish between a "monoculture" and a "standard"?

I feel the same instinctive feeling that we're just going back to the IE days, but is it possible that having all browsers align on a single rendering engine could prove to be helpful rather than harmful?

Indeed. We should be able to split our browser choices freely between a duopoly!
About 5 years ago we had 4 browsers with significant share - IE, Chrome, Firefox, Safari. Even 10 years ago Firefox had a decent impact over over 25% and IE was being brought down into the "managable" area of 50%ish.
I'm screaming on the inside. And using chrome because my phone doesn't have enough storage for another browser / I can't remove it.

Which is baffling: I find myself in a situation that Microsoft was fined for

uMatrix is the best at blocking all sorts of content. One can selectively enable and save preferences per website, and that is helpful since uMatrix tends to break websites using CDNs.
s/mobile/Android/

Unfortunately there are no extensions on iOS (I'm guessing due to Apple's policies).