“Self-reliant and controllable” — the phrase itself isn’t wrong; the subject is. Controllable should mean controllable by the user. How did it come to mean controllable by the company that built it?
The original meaning is clear: you have the code, you can modify it, you can audit whether it’s safe, and if another country cuts you off, you can still use it. The fashionable version today? You get controlled, you pay a 30 percent toll, and you’re not allowed to ask what’s inside. That isn’t self-reliance. That’s Big Brother.
Someone will say closed is safer — open it up and the enemy sees it too. It’s the reverse. An open kernel is what’s safe, because when it’s open, all of humanity can see it. When it’s closed, only the vendor knows. A kernel that exactly one company on Earth can fix means that if a backdoor exists, the patch schedule follows that company’s development calendar.
Push the definition and it gets funnier: by this standard, who is most self-reliant? The code that’s laid open. AOSP — source out in the open, anyone can take it, modify it, audit it. Escaping AOSP’s “control” only to end up less self-reliant than AOSP: a win on the banner, a loss on the definition.
So to judge whether a system is controllable, don’t ask which company owns it and don’t listen to its slogans. Ask one question: does it dare to lay its kernel open?
The user can see it, modify it, and keep using it through a cutoff — that is self-reliance. The subject is the user. Not the company.
