3 ms·

>use profiles for what profiles are good at This is what I'm saying and what people who recommend containers as a "replacement" for profiles sorely miss. >20

by pxoe 1y ago

>use profiles for what profiles are good at This is what I'm saying and what people who recommend containers as a "replacement" for profiles sorely miss. >20 minutes to set up Meanwhile on Chrome this just worked out of the box and didn't have UI that's been abandoned for a decade.

quesera 1y ago
Selecting a profile at launch has never been a problem in Firefox. Switching to a different profile in a running browser is prettier in Chrome though, sure. The bigger problem for me is that (at least when I last tested Chrome profiles -- it's been a while), there was some browser config that was shared between profiles. Maybe extensions? I don't recall. This was unexpected and undesired, so I went back to Firefox.
- celsoazevedo 1y ago
  That depends a lot on the platform. On MacOS, for example, switching to a profile from about:profiles results in the new window being open in the background and it would mess your Firefox icon on the dock. The solution used by Windows and Linux users (the -p command) also doesn't work here (maybe it does via the terminal, but not with shortcuts). Anyway, there's no benefit to Firefox or its users if profile switching is ugly or clunky. They're improving this and that's a good thing for everyone.
  - quesera 1y ago
    On macOS, sending `--no-remote -P <profilename>` in the command line is the method for launching specific profiles. I add an icon (slightly modified for each profile) to the script, and rename it to (e.g.) ~/Applications/Firefox-work.app for convenience. Works from the Dock, Finder, Spotlight, etc. I usually launch from the command line, but all the usual ways do work. Improving the profile switching experience is great of course. But the above workaround has served me perfectly for as long as I can remember. Obv would not work for everyone.

3 ms·

>use profiles for what profiles are good at This is what I'm saying and what people who recommend containers as a "replacement" for profiles sorely miss. >20

by pxoe 1y ago

quesera 1y ago
Selecting a profile at launch has never been a problem in Firefox. Switching to a different profile in a running browser is prettier in Chrome though, sure. The bigger problem for me is that (at least when I last tested Chrome profiles -- it's been a while), there was some browser config that was shared between profiles. Maybe extensions? I don't recall. This was unexpected and undesired, so I went back to Firefox.
- celsoazevedo 1y ago
  That depends a lot on the platform. On MacOS, for example, switching to a profile from about:profiles results in the new window being open in the background and it would mess your Firefox icon on the dock. The solution used by Windows and Linux users (the -p command) also doesn't work here (maybe it does via the terminal, but not with shortcuts). Anyway, there's no benefit to Firefox or its users if profile switching is ugly or clunky. They're improving this and that's a good thing for everyone.
  - quesera 1y ago
    On macOS, sending `--no-remote -P <profilename>` in the command line is the method for launching specific profiles. I add an icon (slightly modified for each profile) to the script, and rename it to (e.g.) ~/Applications/Firefox-work.app for convenience. Works from the Dock, Finder, Spotlight, etc. I usually launch from the command line, but all the usual ways do work. Improving the profile switching experience is great of course. But the above workaround has served me perfectly for as long as I can remember. Obv would not work for everyone.