I agree that Chrome fucking sucks, but it’s disingenuous to call it unoptimized. Chrome and chromium-based browsers are as fast as or faster than Firefox. Although I agree that manifest V3 is horrible to the web as a whole and shouldn’t have been created.
I was exaggerating to make a point. But one of the main reasons why I switched to Firefox (about a year ago) was because it was eating up so much of my CPU.
I use 10ten (previously Rikuchamp) for Japanese. I don’t think it does full translation, but it gives thorough dictionary lookups (from WWWJDIC) as mouseover tooltips. Very useful if you’re trying to learn the language, but maybe not so much if you just want to read stuff quickly. I think it’s now available for every major browser, but I mostly use it on FF.
AFAIK the built-in translator doesn’t support Japanese, which is 99% of translation I need and the extension (which is what is was trying to use before) either requires you to select the text that you want to translate one-by-one or run the whole page through translate.google.com, which doesn’t work with any page that requires an account to access or triggers ddos protection on some others.
That’s not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.
I don’t know the history of column span but the reason Firefox was “behind” on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.
It was Google doing their variation of “embrace, extend, extinguish”
It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.
Google was actually later to implement this particular standard than Edge and Safari, at least according to MDN. And I believe this was before Chredge.
Totally agree. It’s not the fault of Firefox at all. This is just being trigger-happy on new standards before they are ready and unwillingness to fix a problem in a different way.
It got added because it worked extremely well on browsers that implemented it, and it solved a problem that was needed on the site in question, which was very difficult to solve otherwise. I can’t blame a site for using an open standard that works for a majority of its users and which makes the development effort significantly less.
If your website only works with Chrome, it’s not a website. It’s a Chrome site.
You didn’t design for the web. You designed for Chrome.
Fuck chrome. Such a dogshit unoptimized spyware browser that now disables ad-blocking plugins
I agree that Chrome fucking sucks, but it’s disingenuous to call it unoptimized. Chrome and chromium-based browsers are as fast as or faster than Firefox. Although I agree that manifest V3 is horrible to the web as a whole and shouldn’t have been created.
It also eats up like 99% of your CPU
Single browser open? Lemme fire up a dozen .exe processes there…
Have you used chrome or chromium in the past few years? Source?
I was exaggerating to make a point. But one of the main reasons why I switched to Firefox (about a year ago) was because it was eating up so much of my CPU.
Their plugins were fucked from the beginning. You never had control of your extensions.
The problem for me is that the built-in translator is too convenient
Pretty sure Firefox have that too
*For a limited set of languages. Until they add Japanese I won’t be getting much use from it, sadly.
I use 10ten (previously Rikuchamp) for Japanese. I don’t think it does full translation, but it gives thorough dictionary lookups (from WWWJDIC) as mouseover tooltips. Very useful if you’re trying to learn the language, but maybe not so much if you just want to read stuff quickly. I think it’s now available for every major browser, but I mostly use it on FF.
Firefox has translation now, too, on both mobile and desktop.
And you can optionally add the Google Translate extension to desktop Firefox if you want. (It really is convenient, isn’t it?)
And you can always just plug in the URL of whatever page you’re trying to translate directly into https://translate.google.com/.
Safari also has it built in. This person is just saying shit to say shit I guess.
AFAIK the built-in translator doesn’t support Japanese, which is 99% of translation I need and the extension (which is what is was trying to use before) either requires you to select the text that you want to translate one-by-one or run the whole page through translate.google.com, which doesn’t work with any page that requires an account to access or triggers ddos protection on some others.
Yeah, I think Firefox’s translation feature is technically still in beta.
Real. Only thing i pop microsoft edge open for. Firefox’s one is too slow.
Chrome is awful in nearly every way one can measure a browser. Anyone still using this as they’re main driver in 2025 is technologically challenged.
It’s wild to see Chrome going from the browser to use if you had any tech sense whatsoever to being universally derided.
I just design for IE6
An Antiquarian I see. Carry on my good fellow!
I do this, but unironically.
I code raw html in notepad as god intended
That’s not necessarily true. Circa 2016–17 I frequented a website that worked in Chrome but not Firefox. This was due to Firefox at the time not implementing web standards that Chrome did. Firefox only got around to it in 2019. So naturally, the developer of the site was telling people to use Chrome.
I don’t know the history of column span but the reason Firefox was “behind” on standards was because Google was pushing new standards through committee faster than competing browsers could keep up. Google would implement a new feature, offer it as a free standard, then get it through the committee. Because Google already had it in their browser, they were already compliant while Firefox had to scramble.
It was Google doing their variation of “embrace, extend, extinguish”
It got so bad that not even Microsoft had the resources to keep up. They said as much when they said they were adopting Chromium as their engine.
Google was actually later to implement this particular standard than Edge and Safari, at least according to MDN. And I believe this was before Chredge.
Chredge :D
Yeah it’s a very fun name, isn’t it?
I’m gonna be honest, if they used a feature that wasn’t ready for prime time, it’s still on them.
Totally agree. It’s not the fault of Firefox at all. This is just being trigger-happy on new standards before they are ready and unwillingness to fix a problem in a different way.
It got added because it worked extremely well on browsers that implemented it, and it solved a problem that was needed on the site in question, which was very difficult to solve otherwise. I can’t blame a site for using an open standard that works for a majority of its users and which makes the development effort significantly less.
You don’t change standards to fix bad code
If only one browser runs it, it’s not a standard