I just wish Firefox would support HDR, more than 60hz refresh rate and more than two channel audio.
It could easily support launching dedicated media player such as mpv or mplayer. I wonder why this trivial functionality isn't part of any browser.
The endless browser wars
231–240 of 242 posts
Re: The endless browser wars
#232Re: The endless browser wars
#233I always considered Chromium to be a sort of castrated Chrome, now it's even more apparent than ever.
Re: The endless browser wars
#234> The larger problem, though, is that it's not at all clear that Firefox will remain a viable alternative to Chrome. Its market share has been falling for years, and not everybody is pleased with the directions that the Mozilla Foundation has taken. I'm disappointed by how many people cling to Chrome/Chromium under the justification that they don't like where Mozilla is going. If you can't tolerate Firefox because of…
Also, just changing to a Chromium based browser is not sufficient. Google still takes most of the decisions in where Chromium is going, and downstreams either accept them or workaround them (but for every workaround they do it is more things to keep maintaining in the long run). So yeah, using a non Chromium browser is the only way to ensure that the Web is still healthy (i.e.: not controlled by only Google) in the l…
> using a non Chromium browser is the only way to ensure that the Web is still healthy
Just using some other browser isn't enough. Unfortunately not all webmasters take this seriously, I reported many website issues as a Firefox user to many orgs, even university departments, the most common answer is "Just use Chrome". The ignorance is enormous.
Re: The endless browser wars
#235Earlier quoted context omitted.
How about Brave as a Chromium-based alternative to Firefox that isn't worse for the cause?
That would require nuanced discussion. We can't have that! (Kidding aside, I happily use Brave because I find Firefox borderline unusable, but also find Google's tactics unpalatable.) The larger issue is there shouldn't be a war. There should be as many browsers as people have the hearts desire to create, and it shouldn't matter because they all follow the same standards. However, in the real world, we've seen the no…
But browsers are by nature an engineering project several level divorced from hardware. There is no natural law demanding that they have to be democratic. Ultimately somebody has to foot the bill for their development time. C++ developers are not exactly a scarce commodity yet you don't see any major governments willing to fund browser development despite it being a critical piece of infrastructure. "Professional services" companies like IBM, Deloitte, Oracle, Accenture, get paid hundreds of millions to billions a year to build CRUD software for the public sector. Maybe it is time to redirect some of those funding to more useful purposes.
Re: The endless browser wars
#236Earlier quoted context omitted.
Apple's webkit is open source as well. All major browsers are based on open source engines. The situation could be much worse.
And Webkit itself started a fork of KHTML, if I recall correctly.
Correct. As a former die-hard KDE user, KHTML/Konqueror was my daily browser, until I switched to OS X Tiger. Been using Safari since that. Also for web development.
Re: The endless browser wars
#237Earlier quoted context omitted.
Out of curiosity, what is it that makes Firefox 5% worse than Chromium-based browsers in your eyes?
Slightly slower page loads (5% times all day remember) Less usable ctrl+tab behaviour for managing lots of tabs 20 second pause to start if not already running on many of my locked down systems over the years, seems to have been fixed in last year or so but perennial problem that was infuriating in the same way nag-ware delays are F** with the extensions Ongoing 'minor' user-unfriendly decisions to the actual users o…
I had the pause problem about when you had it as well. For me the pause happened periodically, but it was for network requests IIRC, the rest of the browser worked fine, but pages wouldn't load a thing for quite a few seconds. I have not noticed the problem now for quite a few months at least. Since it looks like the pause went away at the same time, I think we had the same problem.
Re: The endless browser wars
#238Holding strong to Firefox as long as I have to. What really strikes me is why more people aren't pushing for open-source browsers. One would think that it is important to have an element of trust for something that makes up the bulk of your computer's uptime, but perhaps open source is no longer a good indicator of trust for projects as large and complex as modern browsers, or people are willing to trust them anyway.…
I switched over to Waterfox after their recent blog post[0]. Not a political matter, it just reeked of paternalism. I'll hold on to Gecko as long as I can, but Mozilla keeps making decisions that force me to hold my nose. [0] https://blog.mozilla.org/blog/2021/01/08/we-need-more-than-d...
"we need more than deplatforming" and auto-enabling fact checkers which thus far are plainly partisan hacks is a nope. They're just fine creating a political monoculture, and I can't get the taste of vomit out of my mouth. The browser used to stand for privacy and choice first and foremost. We'll see how they end up but I don't want to support shit like that.
Re: The endless browser wars
#239Wonder why he didn't mention, Ungoogled Chromium, the most likely successor of all linux Chromium packages.
In between I am slowly moving to Firefox on Fedora, but mostly because I can watch HD videos there, not on Chromium. Firefox is also much faster than Chromium.
Re: The endless browser wars
#240Earlier quoted context omitted.
I encounter it occasionally. Either broken or omitted features. Slack calls don't work in Firefox just because. Blurring out your background in Google meet isn't available on Firefox. Some utilities websites here, in Ireland, don't work in Firefox but do in Chrome.
>Slack calls don't work in Firefox just because. Slack calls don't work in Firefox because Slack explicitly made the choice to not support Firefox and to not follow web standards in how they implemented Slack calls. Furthermore, they go a step further by detecting your browser and blocking the feature for Firefox users and telling you to switch to Chrome. [1] This is not a failure of Firefox, it's a failure of Slack.…
I know its a failure of Slack, which is why I responded to the parent