[b3ing]

Hopefully this means people return to FireFox, which I'm surprised many developers abandoned.

[smallerfish]

I certainly will switch to Firefox (which I already use on my phone) if ad blocking stops working in Chrome. I'm really only on Chrome out of inertia - the developer tools in Firefox is just different enough that I haven't put in enough time to learn my way around it.

[metadat]

The dev tools in Firefox are actually nicer in some cases..

<Right-click Q> -> Boom, console open inspecting the element under the cusrsor.

Chrome requires more clicks.

[Tanoc]

Just hit F12. Even faster, and it'll remember if you were in the console or the inspector the last time you closed it on that page. I use it quite a bit to just delete elements for pages I'm only going to visit once or twice, but don't want to spend time messing with my adblocker on.

[reustle]

When the news broke again of this change, I made yet another attempt to return to Firefox. Fortunately, I never returned. They’ve improved quite a bit in terms of resource usage and functionality, and I’m not looking back.

[paulryanrogers]

So you returned to Firefox and stayed? I.e. did not return back to Chrome?

[reustle]

Sorry, that was poorly worded. I have been using Firefox happily ever since.

[lagniappe]

this was even funnier the first time i read it and understood it as mozilla developers, as a joke on resource allocation.

[pjmlp]

Unfortunately I seriously doubt it, given how many advocate for Google's efforts to make Web into ChromeOS, buy Chromebooks, and ship desktop applications wrapped in Electron.