News for hackers. Stuff that matters.
Re:Chrome is deploying HTTP/3 and IETF QUIC by garmaine on Wednesday October 07, 2020 @03:39PM (#24711868)
Firefox has been a dead browser walking for a number of years now.

I don’t like this any more than you, but it’s the truth.

Re:Chrome is deploying HTTP/3 and IETF QUIC by dont__panic on Wednesday October 07, 2020 @03:59PM (#24712068)
I'm not sure if this is true -- there was a dark time during the period where Google started to advertise Chrome on literally all google websites, but all of the internal refactors and engine improvements over the past 2-3 years have made an enormous impact on my user experience. And as far as I'm concerned, Firefox isn't dead as long as there isn't a viable replacement that:

- doesn't update via a sketchy background process (Google Updater, or whatever they've renamed it to this month to avoid scrutiny)

- allows me to customize the UI to fit my needs (tree style tabs are an absolute must for me)

- allows me to use a full ad blocker like uBlock Origin instead of arbitrarily limiting the ad blocker API to advance the interests of advertisers

Of course, Firefox's management is an enormous problem, from the way they've prioritized features to the recent layoffs to the enormously stupid decisions (letting a certificate expire that disabled almost all add-ons, the Mr. Robot tie-in "experiment", pushing pocket, default disabling userChrome.css, forcing auto-updates) they've made in the past 5 years. But the core of Firefox is good.

I would love a startup that builds an entire business off of a fork of Firefox that's completely based on privacy, perhaps with some non-invasive monetization like:

- a $5-20 one-time fee to use (with weak enforcement, a la Sublime Text's "annoy you every 5 saves" model)

- a paid vs. free split where the free version of the browser adblocks ads but replaces them with in-network, verified safe ads

- Linux kernel donation-style only model, with no parent corporation

Because of all of the Firefox devs floating around who just got laid off, you could even snatch up some guaranteed capable talent already familiar with the code base. And the best part? They're already vetted to not be part of the management-industrial complex that's taken over Firefox these days.

Re:Chrome is deploying HTTP/3 and IETF QUIC by shadowgovt on Wednesday October 07, 2020 @04:27PM (#24712343)
Sub-10% market share is a problem for them.

It's enough of a skew that when rendering errors crop up, product managers have to decide how many eng-hours it's worth to chase down the small implementation difference between Chromium and Gecko to snag 1 in 10 potential lost visitors, instead of throwing a UA-sniffing "best viewed in Chrome" banner on the page and calling it a day.

Being a rarely-used browser is a negative feedback loop for compatibility, regardless of what standards say (because standards are often too loose to guarantee full interoperability in all corner cases; they rarely give performance constraints and often don't consider all possible combinations of feature use).

Re:Chrome is deploying HTTP/3 and IETF QUIC by mrec on Wednesday October 07, 2020 @05:24PM (#24712909)
Agree on all points. It's not quite as deadly as back in the old browser wars, because HTML5 is much better specified than its predecessors, but it's definitely a major problem.
Re:Chrome is deploying HTTP/3 and IETF QUIC by asddubs on Wednesday October 07, 2020 @05:24PM (#24712908)
>- a paid vs. free split where the free version of the browser adblocks ads but replaces them with in-network, verified safe ads

your ideal privacy focused firefox comes with a conflict of interest built in

Re:Chrome is deploying HTTP/3 and IETF QUIC by fakedang on Wednesday October 07, 2020 @04:28PM (#24712349)
> I would love a startup that builds an entire business off of a fork of Firefox that's completely based on privacy, perhaps with some non-invasive monetization like:

Don't know if this is 100% accurate, but Tor?

Re:Chrome is deploying HTTP/3 and IETF QUIC by Fnoord on Sunday October 11, 2020 @10:05AM (#24745858)
> Don't know if this is 100% accurate, but Tor?

You probably meant "Tor Browser". Changes from there were backported, and last time I checked plan was to have it entirely backported within Mozilla Firefox.

Re:Chrome is deploying HTTP/3 and IETF QUIC by freeopinion on Wednesday October 07, 2020 @04:40PM (#24712470)
You mean like Brave, only built off Firefox?
Re:Chrome is deploying HTTP/3 and IETF QUIC by dont__panic on Wednesday October 07, 2020 @05:54PM (#24713205)
Pretty much my vision. The largest reason I don't use Brave is because it's built on top of Chromium, and simply jumping on the Chromium train gives Google the ability to dictate the future of the internet. There needs to be a browser engine alternative, or alternatively, maybe we need to spin Chromium out of the Googleplex and let a free and open source group handle future development independent of the Ad overlords.
Re:Chrome is deploying HTTP/3 and IETF QUIC by freeopinion on Thursday October 08, 2020 @01:10PM (#24721288)
I understand your sentiment, but let's be clear. Chrome was itself a "spin out" from another engine. That engine still exists. But Google's investment into Chrome has been such that you yourself ignore the original. A new spinout from Chrome would face the same problems.