Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pausing Manifest V2 phase-out changes

groups.google.com

Post reply on HN
Print view View original

81–90 of 170 posts

Re: Pausing Manifest V2 phase-out changes

#81

Post by davidgerard »

xchkr1337 wrote: post #56
kej wrote: post #46

Earlier quoted context omitted.

You can just do this anyway, you know. Firefox is pretty great these days.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

> bad font rendering

would I be correct in guessing that you're using the snap? It's pretty, uh, garbage. The Chromium snap keeps having font problems too.

Re: Pausing Manifest V2 phase-out changes

#82

Post by noman-land »

qwertox wrote: post #44

> As we head towards Manifest V3 migration, we are intently monitoring comments from the developer community to help inform our timelines. Here's some feedback: If uBlock Origin loses full control over what gets loaded and what not, I will immediately uninstall Chrome from all my and my family's devices and switch back to Firefox, after a decade of using Chrome as the main browser. I will then also recommend the excl…

Why would you wait for this one single thing when you have had so many historical reasons to choose Firefox over Google already? Why wait for Google to piss you off for the thousandth time when 999 times is plenty?

Re: Pausing Manifest V2 phase-out changes

#83

Post by nozzlegear »

darreninthenet wrote: post #74
judge2020 wrote: post #51

Earlier quoted context omitted.

Especially on macs

I found it's lack of support for native functionality in MacOS too irritating (eg doesn't support system wide autocomplete - so my @@ shortcut that puts my email address in doesn't work in FF - I know I could put it in again in FF but it's annoying it just doesn't work) so I went back to Chrome in the end. I was using Edge for a while but the absolute car crash their UI has become - and can't be configured - sent me…

My biggest complaint with Firefox on macOS is the lack of support for native picture-in-picture. They implement their own version that doesn’t stay visible when you swap between the virtual desktops; won’t overlay on top of full screen applications; and can’t be moved across monitors (iirc) either.

Re: Pausing Manifest V2 phase-out changes

#84

Post by GeoAtreides »

xchkr1337 wrote: post #56
kej wrote: post #46

Earlier quoted context omitted.

You can just do this anyway, you know. Firefox is pretty great these days.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

I have been main driving Firefox on Linux for the past six years, on Lubuntu, without any kind of problems. None whatsoever. It's fast and it's rock solid stable.

Edit: some people mentioned it's Firefox snap that has problems. I'm using the apt-get package one.

Re: Pausing Manifest V2 phase-out changes

#85

Post by paulryanrogers »

shadowgovt wrote: post #65
voytec wrote: post #31

Earlier quoted context omitted.

But will likely be plagued with performance degrading ads.

And it's still fast in spite of that, which speaks to how far behind Mozilla is.

Part of the difference is that the modern web is built for Chrome. Even checking ones site or service with Firefox for functionality is a bridge too far, much less performance.

Re: Pausing Manifest V2 phase-out changes

#86

Post by tigrezno »

davidgerard wrote: post #81
xchkr1337 wrote: post #56

Earlier quoted context omitted.

I wish Mozilla focused more on Linux support. I tried switching to Firefox multiple times, and in day-to-day use I always keep running into unfixable problems like bad font rendering, slow webgl performance, ui glitches etc. Problems like this never happen when I'm using Firefox on Windows, and honestly the state of Firefox on Linux is kind of surprising since it's the most commonly recommended and preinstalled brows…

> bad font rendering would I be correct in guessing that you're using the snap? It's pretty, uh, garbage. The Chromium snap keeps having font problems too.

this is fun because the snap works perfectly on my machine, and it's fast as the native version. I think the snap version is far better than running it natively (more secure). A web browser is a hacker's dream.

Re: Pausing Manifest V2 phase-out changes

#87

Post by kgwxd »

20after4 wrote: post #69
20after4 wrote: post #60

Earlier quoted context omitted.

I'm using Firefox on Linux¹ and I have experienced none of those problems. Although I'm not particularly happy with the direction that Mozilla has been headed, Firefox is certainly a vast improvement over Chrome or even Chromium. 1. Latest version of Firefox (not ESR), Latest Debian, both Intel & AMD graphics. I can't speak for NVIDIA graphics on Linux as I gave up on NVIDIA a few years ago.

Admittedly there were a few issues in the past, just nothing in the last couple of years that I can think of.

I was on Linux for about 10 years without a single issues with Firefox until it was turned into a snap package. Slow as hell startup times and other oddities. Removed that and installed from apt and it was back to perfectly stable. Font rendering was always different but I wouldn't say worse. In fact, now that I'm fully back on Windows, the font rendering on Linux is the only thing I really miss. Windows seems a bit blurry in comparison.

Re: Pausing Manifest V2 phase-out changes

#88

Post by malermeister »

Kye wrote: post #34
brucethemoose2 wrote: post #6

Earlier quoted context omitted.

This seems to be a pattern among Google employees, as least as I'm seeing from the outside. They have their own company reality bubble, and clashes or inconsistencies with the outside world are met with disbelief.

I remember getting into it with a Google person in a forum once. They kept insisting they couldn't do real, portable files in Google Drive for Docs because that would break collaboration. They didn't seem able to understand I didn't want collaboration. I wanted to be able to open my word processor/spreadsheet/etc files in other tools without needing to connect to the internet (predates offline mode). I wanted to be a…

It is difficult to get a man to understand something, when his salary depends on his not understanding it.

Re: Pausing Manifest V2 phase-out changes

#89

Post by kgwxd »

kivle wrote: post #52
pkulak wrote: post #27

Earlier quoted context omitted.

Why wait? Move to Firefox now.

Using 2-3x as much battery as all other browsers on my Macbook is the dealbreaker for me.. I want to use the same browser on all systems when I move..

You should get off mac for the same reasons to get off chrome.
Post reply on HN