>In this sense, "Just works" relates to restrictions on users.
No. Still attacking a symptom. Standard compliance solves the same problem, without having to lock down the system. If programmers are unable or unwilling to conform to standards, then this is again not the fault of the system[1]. Give up on arguing that there is any sort of causation between "locked" and "just works". It's wrong.
[1] Actually, in this case it's the fault of the system. The lock places a false sense of security on programmers, which is pretty dangerous.
But standards compliance is a sort of restriction on the apps the user can run. If you make the standards stricter and stricter, you restrict the space of configurations more -- and make it easier to get configurations that work together.
The difference is that nobody forces you to comply to standards. If you want to hack around on your device, install third party software, concoct your own APIs and drivers or patch the kernel, nobody can stop you (and shouldn't be allowed to, either). While you can argue that a restrictive system is a sort of standard as well, you are forced to comply to that standard with no alternative, and that's bad.
Besides, standards, at least open ones, are usually collaborative efforts of multiple actively involved parties, while restricted systems are controlled by a single entity - which again is bad.
In this sense, "Just works" relates to restrictions on users.