The profile UX on Chrome is almost as horrible as it is on Firefox from a user's perspective, namely you need to reinstall all your addons and have no shared history so you need to check twice every time you're looking for something. The only difference is that on Chrome, it's the only way to have two different accounts on the same site, whereas on Firefox you generally don't need it unless you need the highest level of separation.

Profiles and Containers are different things.

If more people understood this, we would be asking for better profile support on Firefox and for container support on Chromium, not suggesting containers to people who need profiles or trying to use profiles as if they were tab containers.

I want profiles because they provide exactly what you mentioned: separation. I need different extensions, bookmarks, history, etc. And inside each profile I can use containers if I want to.

If you want profiles and not containers, you can use profiles too in Firefox, it works well (I do it on the shared family computer). It's just not what most people use profiles for in Chrome, which lacks the separation between profiles and container.

> you can use profiles too in Firefox, it works well

So explain me:

1. How do I set up a new profile in Firefox. In Chrome creating a new Profile takes 3 clicks and entering a name.

2. How I open two instances/windows of Firefox at the same time each with a different profile. In Chrome opening a second profile is two clicks (when Chrome is already running)

Type about:profiles in the address bar, and then you're one click away from both of your questions.

And that's the point: No normal user will ever discover that feature

Normal user don't explore the menus trying to discover the stuff they might like.

They either get hinted by someone else about “some cool feature”, or do a Google search if they know what they're looking for.