One implementation detail bothered me longer than it should have. Not because it was hard to understand, but because it quietly changed what "staying inside a system" means.
Most lock-in gets blamed on rules — closed APIs, proprietary formats, restrictions that make leaving impossible. Those are the easy ones to spot. What I didn't expect was to find the same question hiding inside a storage decision.
In OpenGradient's Walrus layer, an artifact isn't permanently tied to the app that first produced it. Switch environments, and the rest of the stack can stay where it is. The technical part is almost invisible. What it does to behavior isn't.
So I keep wondering how many ecosystems survive without forcing anyone to stay. Every extra dependency, every migration step, every small inconvenience nudges the next decision until it stops feeling like a decision at all.
Lock-in rarely starts with a restriction. It starts with friction so ordinary you stop reading it as a choice. And the systems I find myself trusting aren't the ones that keep people in. They're the ones that reveal how much effort leaving quietly used to cost.
$OPG #OPG @OpenGradient