←back to thread

"Begin disabling installed extensions still using Manifest V2 in Chrome stable"

(developer.chrome.com)
552 points freedomben | 2 comments | 11 Oct 24 14:20 UTC | HN request time: 0.416s | source
Show context
bijection ◴[11 Oct 24 19:04 UTC] No.41812422[source]▶
I've finally switched (back) to firefox today.

I switched from firefox to chrome for their superior devtools a few years back, but hopefully firefox has had time to catch up.

Everything old is new again!

replies(4): >>41812698 #>>41813042 #>>41813500 #>>41816262 #
ttt3ts ◴[11 Oct 24 19:56 UTC] No.41813042[source]▶
IMO they are still not as good although they have improved. I just develop in chrome and use Firefox for everything else.
replies(4): >>41813331 #>>41813511 #>>41814354 #>>41815308 #
1. KTibow ◴[11 Oct 24 20:21 UTC] No.41813331[source]▶
What makes them less good? I'm used to Firefox and while the Chrome devtools have more features they're harder to use (eg smaller touch targets, can't accept JS suggestion with enter key)
replies(1): >>41815087 #
2. tonightstoast ◴[11 Oct 24 23:51 UTC] No.41815087[source]▶
I use FF and my coworker uses Chrome. He says the thing that pisses him off the most when watching me use FF is that there is no fuzzy search when manually applying styles. I.e. you have to search "justif..." to see "justify-self". You can't just search "self". That's the only example I've really noticed between the two but I'm sure there are more. It doesn't bother me enough to change though.