I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
Safari redesigned their dev tools at some point a long time ago and made the interface (IMO) terrible. Until they did that I used to use it a lot more. Safari is a great browser if you don’t need the most cutting edge features or extensibility though, and I believe it’s also the best optimized for battery life.
Switch from Chrome to Firefox
231–240 of 1001 posts
Re: Switch from Chrome to Firefox
#232I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
If uBlock stops working, I'll switch off in an instant though.
Re: Switch from Chrome to Firefox
#233I switched a couple of months ago because Chrome is just a bloated piece of garbage. One of my favorite features in Firefox is containers, which I used to have different users for in Chrome. Maybe Chrome has something similar now but it's one of the things I liked when I switched over. Haven't had any issues so far, glad I did
I switched a couple months ago from Chrome to Firefox as well but to tell you the truth, I just heard about containers and what you could do with it. I guess I must've been living under a rock, this is amazing!
I was already glad I made the switch for the less resources being used on my aging Macbook Pro and better privacy features, but containers just took this experience to the next level for me!
EDIT: What actually triggered my switch was at one point, a few tabs on Chrome(regular things like Youtube) started causing my CPU/fan to go crazy on my MBP 2015(the last decent MBP). Instead of trying to figure out what extension or what setting was causing the problem, I thought I'd give FF a try and just couldn't look back after.
Re: Switch from Chrome to Firefox
#234Am I missing something here? There is no article just a download link correct? I use Firefox exclusively because of the sidebar tab extension and will probably use it until Firefox dies a slow death.
Chrome's "Press Tab To Search" is way too useful for me to switch...
I've switched to DuckDuckGo, and using their ! operators (!w for Wikipedia, !map for Google Maps) picks up most of the slack.
Re: Switch from Chrome to Firefox
#235Earlier quoted context omitted.
The "magic" is Source Maps. Firefox supports Source Maps just fine, it's just pickier about their formats. It was supposed to be a standard and all the browsers supported it (Edge and Firefox have had support for as long as Chrome has). Chrome allowed some Source Map formats that didn't exactly follow the standards/specs, and a bunch of tools started using Chrome-only Source Maps by default accidentally because so ma…
How strange, this is the first I've heard of this. I've never had to touch source maps config in my webpack and it's always shown fine in Firefox. Is it just specific circumstances/specific code patterns that have source map problems in Firefox? Or is it when it's transpiling from TypeScript or JSX or something?
In some cases it looks like Chrome takes extra efforts to find physical files on disk from bad URLs, and in other cases Chrome does more with virtual file structures included in the same bundles (the webpack:// pseudo-URLs often point to other "sections" of the same JS bundle) creating a virtual file tree from them that looks close enough to the on-disk file tree as to seem effectively the same to many developers.
Re: Switch from Chrome to Firefox
#236Earlier quoted context omitted.
I don't understand how it's better than multiple profiles. I use multiple accounts for the same services (Asana, AWS, email, etc.) how can I manage that with containers?
In my opinion, profiles are useful for separating "who I am." Whether that's my personal life and my professional life, or if it's me or my spouse using the same computer. Containers are useful for separating "who I am to my providers." As far as Facebook is concerned, I am a Facebook user, but I don't use Amazon or Google. But Amazon thinks I'm an Amazon user that doesn't use Facebook or Google. You can accomplish t…
Re: Switch from Chrome to Firefox
#237One HUGE issue over Chrome is that many websites break for me due to broken JS that was only tested on Chrome, including internal sites for work. Ugh.
The visuals of FF including their website are beautiful. Wish they would put that same design team on Rust, which has a website made by a clown now.
Re: Switch from Chrome to Firefox
#238Still there's one thing that Firefox can beat, Chrome dev tools are just the best, period.
Re: Switch from Chrome to Firefox
#239Why is leaving the only recourse? Chromium is free software. Forking always remains an option.
Here's a good explanation... https://boingboing.net/2019/05/29/hoarding-software-freedom....
Also, a Chromium fork could use the Widevine binary blob the same way Chrome does today; I am not sure I understand this argument.
Re: Switch from Chrome to Firefox
#240I don't understand why Mac users use Chrome. Safari seems to be out of fashion: people just assume that it should not be used for some reason, even though it is actually a great browser. I use Safari for both my own browsing and for development (a fairly large ClojureScript application), and it is by far the best browser on the platform by all measures (speed first and foremost). The only place where Safari falls sho…
Also as far as I can see I have to upgrade my OS in order to upgrade by browser with safari. Sometimes I just can't be bothered to wait for a 40 minute upgrade to complete.