Switching from Chrome to Firefox
51–60 of 245 posts
Re: Switching from Chrome to Firefox
#52Why the big panda at the top, i dont get it.
Re: Switching from Chrome to Firefox
#53Earlier quoted context omitted.
If you or a random reader is on MacOS, try out Orion - a Safari fork that has support for both Chrome AND Firefox plug-ins. I can't stop using Safari... I know, I'm a dying breed, and people at work were (and still are) a bit weirded out by it, but if you're like me, Orion is a very nice alternative if you want "real" adblockers (and 10000s of other plugins) at your disposal!
Safari is a fine browser, and it’s the best experience on macOS, imo.
Re: Switching from Chrome to Firefox
#54I love Firefox. The only time I struggle it's because it is the only browser today that correctly implements CORS. This is a good thing. But it means broken middle boxes and MiTM enterprise tech (like Zscaler) should fix their stuff rather than pointing their smelly fingers at Firefox. Mozilla should up its game in educating the public that Edge and Chrome aren't following the standards correctly. This seems IMHO pre…
What's the difference in their CORS implementations? As far as I know all three major browser engines follow the modern spec.
Re: Switching from Chrome to Firefox
#55Re: Switching from Chrome to Firefox
#56Earlier quoted context omitted.
As a 15+ years Firefox user: What is "very much off" about Firefox' font rendering? For me it's the opposite, Chrome's rendering looks completely off to me - thin and it looks like the ClearType effect is set to 11. On the other hand, Firefox' font rendering in that screenshot looks like native Windows font rendering to me.
The problem with "very much off" for font rendering is that it is relative to what you are used to, not relative to any actual standard font rendering. If you've been using Firefox a while, Chrome will look off. If you've been using Chrome, Firefox will look off.
Re: Switching from Chrome to Firefox
#57I feel this article almost do more harm than good. It paints a picture that you need to "sacrifice" something to use Fx and lists various "problems". For instance it mentions how troublesome it is to use profiles as a "problem". Don't. Use containers. Hundred times more smooth than profiles. Hence why no one cares about making profiles in Fx better, there is already a better solution to the problem profiles solve. Ne…
(I'm replying to the original version of your comment.) How can you have different bookmarks, extensions, and maybe even a different theme (so you know you're using the right window) with containers? The answer is: you can't. Because containers and profiles are different things. That's the "sacrifice" you're asking users to make. To change the way they use browsers, to adapt to something that is useful, but not a com…
> The answer is: you can't. Because containers and profiles are different things.
If that's what you need then just use Firefox profiles then! The thing is, most people don't need that, and containers offert better ergonomics for the majority use-case (like the one described in the post). But if you still need the niche use-case, then go ahead and use a profile in Firefox too.
Re: Switching from Chrome to Firefox
#58I've always found the Firefox devtools be a little less 'quality of life' like. Just my opinion. Haven't used it in a few years. But for me, I just live in devtools, you know. As most of you here, probably. Opinions?
Re: Switching from Chrome to Firefox
#59I installed Firefox recently but I had to turn off "smooth scrolling" because it was jarring.
Re: Switching from Chrome to Firefox
#60Earlier quoted context omitted.
> Never had problems with font rendering Okay, so what's the logical conclusion here? That the person is lying? The font rendering is very much off, some people just don't notice or don't care. Denying something others see with their own eyes doesn't help anybody.
Chrome's font rendering is the outlier among browsers. The author of the article is seeing that difference and they want Firefox to look like Chrome. I think the commentary is taking an issue with the suggestion that there's something "wrong" with Firefox's font rendering, when it's really Chrome who is the outlier.
As of right now there's substantially more browsers that use Blink (and comprise over half of the market share) though so Firefox and Safari will always be outliers.