51–60 of 733 posts
I was extremely skeptical of all the changes they were doing - I said it myself 100 times, "they're just building a Chrome clone, they're killing all the features I like in favor of speed". But here I am, running Nightly because holy shit this thing flies. Their work has paid off and they're not even done yet. Webrender is coming, it's not quite stable enough for daily use yet (mostly just graphics glitching and inte…
Firefox 57 is great. The interface is no longer ugly, and it's no longer oddly sluggish. Once Lastpass has their extension updated to work with WebExtensions, I'll switch.
Just switched to Firefox beta to test this out. Looking good so far! The other thing that I've been waiting for is better multi-profile support. You can get a (pre-release) version of that now by opting into the Containers experiment: https://testpilot.firefox.com/experiments/containers
I've been using multiple profiles for months on Firefox via `firefox -P profile1`, `firefox -P profile2`. What's it changing to, moving forward?
Firefox has been my daily driver for 2-3 years now. I’d switched to Chrome several years before that but when FF fixed its lag issues I went back right away. Mozilla overplay the “not for profit” card but with Google you can be sure they are collecting and archiving absolutely everything that passes through their servers.
Assuming that one switches to Google as the default search engine (I'd love to know how many do - additionally I beleive Google is the default outside the US anyway), there's effectively no difference. Neither browser does anything special wrt privacy, the same resources and scripts are loaded in both. Safari are the only browser brave enough to try anythng more exciting in this area. (OK, Brave are also in this area…
Firefox users who pick Google as the search engine are still giving a lot of info to Google, but less info than Google would have had if the user was using Chrome.
Just switched to Firefox beta to test this out. Looking good so far! The other thing that I've been waiting for is better multi-profile support. You can get a (pre-release) version of that now by opting into the Containers experiment: https://testpilot.firefox.com/experiments/containers
And it's definitely a reason to switch to Firefox. Keeping personal and work Google and AWS accounts open and separate simultaneously is really nice.
Just switched to Firefox beta to test this out. Looking good so far! The other thing that I've been waiting for is better multi-profile support. You can get a (pre-release) version of that now by opting into the Containers experiment: https://testpilot.firefox.com/experiments/containers
Unfortunately the UI has always been sort of hidden.
You can launch with `-P` or `-ProfileManager` to get a profile selection menu. Or nav to `about:profiles` for a slightly more convenient (but less attractive) version.
Firefox profiles are great. Better than Chrome profiles, though less convenient, for now. Interested to see how Containers fits in.
Does the upcoming Firefox start as fast as Chrome? Rendering was never what I had problems with; startup speed is literally the one reason why I haven't switched.
Do you close your browser that often?
Earlier quoted context omitted.
I've been using multiple profiles for months on Firefox via `firefox -P profile1`, `firefox -P profile2`. What's it changing to, moving forward?
Those aren't changing, the new feature, "Containers", is like having multiple isolated browser sessions running concurrently. So you can organize your tabs by purpose, isolate sensitive accounts, or just be logged into both your Facebook/Google/Twitter accounts at the same time.
What does Containers add? If the only answer is "a more convenient UI", then that's good enough for me!
Earlier quoted context omitted.
One wonders why all the UI issues weren't solved long ago. Good that they're fixing them now, but what were they waiting for to decide to do it? (Rendering performance is a separate topic, that's been waiting on rust/servo.)
One might argue because they were "distracted" with making a phone OS and other endeavors.
The truth is that they were in a dilemma situation where they had to choose between not killing all extensions or fixing performance by introducing a multiprocess architecture (which required breaking all extensions).
So, the first thing they did was to simply wait. The performance issues were not that bad yet, so it just didn't yet weigh up to kill all extensions.
Eventually they started work on the multiprocess architecture. That was around 2012, if I remember correctly. They've been doing that in the background without visible results for the public for a long time. It's considered the biggest architectural change that Firefox ever went through, so yeah, that just takes time. Cleaning up technical debt that Chrome never had.
And then they also figured, if they already break all extensions, they should also switch to a new extension API in the same breath (because the old one has had big problems for as long as its existed). So, then they implemented that, too, in the background, in parallel, just to be able to throw it all on the table one day, so that extension authors would only have to rewrite their stuff once.
Earlier quoted context omitted.
Assuming that one switches to Google as the default search engine (I'd love to know how many do - additionally I beleive Google is the default outside the US anyway), there's effectively no difference. Neither browser does anything special wrt privacy, the same resources and scripts are loaded in both. Safari are the only browser brave enough to try anythng more exciting in this area. (OK, Brave are also in this area…
One can assume Google is tracking a ton of data beyond just what Google searches users do. Firefox users who pick Google as the search engine are still giving a lot of info to Google, but less info than Google would have had if the user was using Chrome.
It's still giving search information to Google, but that's much more preferable to sending literally everything you type in the box.