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

IMO they are still not as good although they have improved. I just develop in chrome and use Firefox for everything else.

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)

Same. I use Chromium for dev and firefox for browsing

I know chrome dev tools are capable, but to me they feel much more dumb and convoluted. There's lots of convenience and golden nuggets in Firefox dev tools that makes you feel they've been designed by and for developers.

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.

I use a little `chrome-new` script to develop (and sometimes take video calls or use buggy apps) against a totally clean fresh Chrome profile, then I use Firefox with uBlock Origin and uMatrix for daily driving.

    #!/bin/sh
    [ -z $CHROME ] && CHROME=chromium
    TMPDIR=$(mktemp -d /dev/shm/chrome-XXXXX)
    $CHROME --user-data-dir=$TMPDIR --no-first-run --no-default-browser-check "$@"
    rm -rf $TMPDIR

The first line lets me override which Chrome version I launch if I want to try instead google-chrome-stable or google-chrome-beta for example. I keep them all installed from the AUR on Arch.

My needs for webdev debugging have always been satisfied by Firefox, but last time I was really in the weeds ~4 years ago I had the feeling both it and Chrome were still missing things I took for granted with Firebug long ago.

I don't mind nice and powerful tools, but one thing I learned with Java (where the tools are so much nicer and so much more powerful) is that if you're leaning on them heavily, that's kind of a sign you've messed up. Like on the scale of severity (https://raw.githubusercontent.com/matthiasn/talk-transcripts...), at least as severe as really bad coupling or brittleness. Thank goodness for the tools that let people efficiently figure things out and get on with things, but it's really better to have not needed to be in such a situation to begin with.

I have a similar view with valgrind -- amazing tool everyone would rather exist than not, one could imagine a "Google Valgrind" and "Mozilla Valgrind" competing on mild differences of amazing, but really, life is better if you can just use a managed language and never have to deal with any flavor of valgrind. I think there are ways to do webdev that significantly reduce the need to use any browser dev tools at all, though the domain necessitates some use. ClojureScript in 2014 was showing the way.

I prefer this way. Much simpler but way more aggressive:

`export HOME=$TMPDIR chrome <args...>`

Will make chrome think that $TMPDIR is $HOME. Keep in mind that means your downloads for example would also be deleted after the rm -rf

This works for most other software too

Better just use 'HOME=$TMPDIR chrome <args... > without the export. With export the Home variable will persist for the current shell, potentially leading to unwanted results.

Right correct. I put this in a script hence the export. Though its probably not necessary as well.