But Firefox has a much better feature: tab containers. You can attach a label to a tab, and only tabs sharing this label will share states, such as cookies, cache, localstorage and so on. This means you don't need to open a new window. You can have 2 HN accounts with each a different user logged in, in 2 tabs, next to each other, distinguishable with a color.
You can use it by activating a few settings in about:config (https://support.mozilla.org/en-US/kb/containers#w_for-advanc...), but the easiest way it to use the addon : https://addons.mozilla.org/fr/firefox/addon/multi-account-co...
https://github.com/mozilla/multi-account-containers/issues/1... https://bugzilla.mozilla.org/show_bug.cgi?id=1283320
Multiple browser profiles also let me have one profile for work, another one for personal stuff, and yet another one only with stuff like vue/react/svelte dev tools and remote debugging enabled, and _then_ decide which one to open at any given time. This instead of opening every container at once, or something like selectively opening a bunch of bookmarks manually into a specific container (I use buku to manage and sync my bookmarks too, so no tab container support there).
Not. On. Android.
Simply start it with "firefox -P" and create two separate profiles (call them "work" and "personal"). Then just start two instances of Firefox, with "firefox -P work" and "firefox -P personal". They will be totally isolated - cookies, history, addons, everything.
Ideally they'd expose more options through web extension APIs or build in a native profile switcher in the main ui rather than as a command line flag and a dedicated about: page. It'd also be cool if the account containers could be customized to behave like profiles e.g. isolate history, but that gets a classic "we need to do this yak shave first" response whenever it gets brought up.
For me, one profile with "Temporary Containers" and "Multi-Account Containers" works well enough.
Alternatively, you can start Firefox with `--no-remote -ProfileManager` flags to get a totally separate instance, like Chrome does.
Personally, I use Multi-Account Containers together with the Temporary Containers add-on, to by default get a fresh cookie jar for each new tab, but I do have some websites tied to a named container for session persistence.
You can also use containers on Firefox for isolating specific sites
Firefox can do that. Just run firefox -p.
>tied to an account
Is that really necessary?
Yes, I'd like extensions, history, cookies, etc to be tied to the account and have them be isolated. I can't do that now.
You can log in into accounts in each profile, of course, if you want.