I tried Orion about a year ago. I tried using the profile sandboxing. Logging into my google account in one profile also logged me in in another profile.

I can definitely excuse some bugs (there were crashes for example that I didn’t overly mind; I understand I was using prerelease software). But something like account containers should be built fundamentally to disallow any data sharing. If data sharing is a bug, and not fundamentally disallowed by the architecture, then it’s going to happen again later.

So for that reason I’m not bullish on orion.

▲

zamadatix 6 days ago | parent [-]

I'd be interested if the issue you ran into was actually due to poor architecture or just something not fully implemented in the pre-release. Unfortunately, it's closed source - so hard to tell from the outside.

▲

rrradical 6 days ago | parent [-]

Well it was definitely a bug. It worked in some cases (I think it even worked in google at first, and then a few days later it manifested). And the feature was advertised, even though, again, they never claimed the software to be release quality.

But my point is that, similar to security, you don't want to build this kind of feature piece meal. Either the containers are fundamentally walled off or they aren't.

	▲	zamadatix 6 days ago \| parent [-]
		I understand what your claim is, I just disagree it's that blanket. You could e.g. absolutely build the UI for a profile switcher before your implementation of the backend changes are merged without carrying implications of how well that will handle isolation in the same way in security you could implement the null cipher in TLS to test that portion of the code without it forever implying you have bad encryption.