←back to thread

552 points freedomben | 2 comments | | HN request time: 0.454s | source
Show context
bijection ◴[] 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 ◴[] 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 #
aftbit ◴[] No.41815308[source]
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.
replies(1): >>41816157 #
pushupentry1219 ◴[] No.41816157[source]
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

replies(1): >>41816906 #
1. zufallsheld ◴[] No.41816906[source]
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.
replies(1): >>41817782 #
2. pushupentry1219 ◴[] No.41817782[source]
Right correct. I put this in a script hence the export. Though its probably not necessary as well.