[rozab]

Profiles definitely have the basic functionality, but I like to keep all my extensions the same across my containers, and it's also easy to set up rules such that a certain site will always open in a certain container. You don't have to think about it at all.

[drdaeman]

I want my extensions to share the base configuration but have some different settings in different contexts.

Like, allow some tracking & advertising for "shopping" container, but block it otherwise. I don't mind having a special self-curated image where my in-scope browsing is tracked and analyzed. Now, I just have a separate browser (Chrome) for this - because it's more straightforward and less error-prone.

Or a sandbox development & local resource management profile where nothing but localhost and LAN addresses are allowed. And then block such access for any other profile - for security reasons.

Or allow, let's say, Grammarly extension on a few selected websites (like HN), where all I write is public and I would benefit from machines aiding my writing without any privacy concerts, but don't give it any chance to see my private correspondence.

Unfortunately, that's not possible with containers, and profiles are quite cumbersome.

[blibble]

excluding extensions is the exact reason I use profiles (I don't want any with access to my banking)

I use containers liberally also

[Farow]

You can open a private window when doing your banking, extensions aren't allowed there by default.

[herewulf]

Good idea but this doesn't save history which can be useful sometimes.