I'd love to talk to you more about the ergonomics of containers / profiles for your use case. You know how to reach me. :)
Thanks for that, I can now replace `chromium --temp-profile`.
Not sure if it meets your use case, but checkout Firefox containers.
Containers only separate Cookies and login data, to make you look towards the internet like multiple people.
Profiles on the other hand separate everything, as if you had two completely independent Firefox installations. Different browsing history, bookmarks, themes, extensions.
They work very well for allowing multiple people to all have their own Firefox, even though it's the same installation. But also really well for single-person use, for example I have a normal Profile for everyday browsing and then a webdev Profile, where I don't put in content/tracking blockers.
You can manage Profiles by typing "about:profiles" into the URL bar or with this: https://support.mozilla.org/en-US/kb/profile-manager-create-...
I'm generally optimistic about Rust code having fewer exploitable defects, although it's a reasonable argument to suggest that the previous C++ parts had a lot more public scrutiny.
Also, for me personally: I use a lot of different profiles and using multiple Firefox profiles simultaneously is a mess. The only UX that still works is about:profiles (all of the profile switcher extensions broke since the move to WebExtensions) and I've had Firefox beachball (hang -- I'm on macOS) on me twice while doing that.
Don't get me wrong! I love Firefox and I'm really excited about this change.