Can we crowdfund a carefully worded firefox advertisement?
Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
181–190 of 394 posts
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#182Earlier quoted context omitted.
why cant brave build on top of firefox?
See Brendan's response to me last week[0], which I think comes down to feature set they want to support rather than do all the work it would require to build that in servo now (they went from gecko [no public info on this] -> electron -> and now chromium. they would have to migrate from chromium -> servo). I wish they did, and just cared less about all the other features that were missing from gecko (but that's just…
cool. so an excel sheet decided google to be the clear winner in present feature comparison set and instead of helping the community in bridging the gap, they decide to go with the flow. cool. i am fine with my ff
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#183I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
I have attempted to move to Firefox twice: once 12 years ago and once 8 years ago (probably, I don't really remember exact time). I know, Firefox has come a long, long, long way since then, but the same were also promised 8 years ago, and it turn out Firefox cannot handle my use case well to the point of almost being unusable. (That said, my use case are definitely not normal) It's a lot of effort to move everything:…
8 years ago, Firefox 25 was released. I don't know your needs but a lot as changed underneath. Notably, Firefox is now using multiple processes, the Javascript engine is probably a lot faster, the web engine too. I don't like every change, especially the latest revamp of the UI, but it is still the best browser for me.
You could try, and them move if conclusive? If you consider switching anyway.
Moving everything before being sure seems expensive.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#184I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
I have attempted to move to Firefox twice: once 12 years ago and once 8 years ago (probably, I don't really remember exact time). I know, Firefox has come a long, long, long way since then, but the same were also promised 8 years ago, and it turn out Firefox cannot handle my use case well to the point of almost being unusable. (That said, my use case are definitely not normal) It's a lot of effort to move everything:…
You can't get even an idea of whether or not it'll work for you without switching over completely?
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#185Earlier quoted context omitted.
I wonder why. It's not like Firefox is a bad browser.
On Android it's freaking fantastic. Everything feels snappier and I can utilise uBlock Origin to block all of the BS. I've set this up for family, friends etc and none have gone back to Chrome. I think the biggest issue is marketing.
The total rewrite might have given some performance boost and if that's worth it for you then I'm glad for you, but unfortunately it also caused loads of bugs and features that have gone missing, and now that the big push for the rewrite is over, tackling those remaining bug fixes and missing features is again happening at a rather glacial rate.
And the frustrating thing is that this used to be a problem even with the previous iteration of Firefox on Android, i.e. it seemed somewhat understaffed and had some surprising bugs (e.g. under memory pressure it would suddenly and silently stop remembering your current tabs) and missing functionality (it didn't remember your scroll position if the app was killed, you couldn't reorder tabs in the tab list) that were only fixed after years, and even then quite a few times only through outside contributions.
And now the rewrite means that all of this has been thrown away and judging from the current development speed it'll take once more years until we sort of get back to where we used to be.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#186I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
I have attempted to move to Firefox twice: once 12 years ago and once 8 years ago (probably, I don't really remember exact time). I know, Firefox has come a long, long, long way since then, but the same were also promised 8 years ago, and it turn out Firefox cannot handle my use case well to the point of almost being unusable. (That said, my use case are definitely not normal) It's a lot of effort to move everything:…
Maybe just dip your toe in? It's okay to use Chrome for X and FF for Y.
i.e. Use it exclusively for HN (say for a few weeks) and see how it goes.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#187Earlier quoted context omitted.
> dev tools Chrome's devtools have been superior (faster, more reliable, more featureful) for years near as I can tell (and everyone I work with). I am curious what makes you feel firefox's devtools are better.
Alternative take: [dev]tools are only as powerful as how well you know them. I'd like to think both firefox devtools and chrome devtools as highly capable, but you'll get way more out of the one you're used to, whichever it is.
The two devtools purport to do almost the exact same things, with a practically identical interface. The details are where the usability differences lie, such as chrome's vastly superior formatting/debugging story. I only moved to Chrome after working with firebug (!) for years and then working with firefox's builtin devtools. If anything, I should hate Chrome's devtools the most because I know them least well.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#188Earlier quoted context omitted.
This isn't a single, monolithic change, there's plenty of changes between manifest V2 and V3. GP said he thought most of these changes are a step in the right direction, while expressing concern about one of the others. That seems like a cohesive and nuanced opinion to me.
It sounds like deflection and rationalization to me. Not all features are equally important, the one seeing a regression is much more important, it's also the feature with a conflict of interest, and the conflict of interest lies in the direction of Google pushing this through over everyone else's objections.
I was in the process of writing a reply when I realised you presented the same arguments in a much more concise manner. For the record, this is what my problem was with the argumentation presented.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#189I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
I deleted Chrome on mobile, I use Safari 100% now.
Re: Google sets burial date for legacy Chrome Extensions, fears for ad-blockers grow
#190I don't understand why this (and all the rest) is not driving people back to Firefox. Are we really going to wait for Mozilla to die, and then lament that Google has taken over the web?
Because many people don't know what's happening and the implications of the new changes on ad blockers are not quite straightforward to explain.