Some neat ideas, but > As long as the OS stays compatible with the old stuff in the context, it can add new functionalities for other App by just appending to

Some neat ideas, but > As long as the OS stays compatible with the old stuff in the context, it can add new functionalities for other App by just appending to the context the new functions Welcome to backwards compatibility hell. You're boxing yourself in this way because you're forbidding yourself to remove old / defunct entries from the Context struct. I think a better approach would be to introduce some kind of semantic versioning between OS and app. The app declares, somehow, what version of the OS it was built against or depends on. The OS then can check if the app is compatible and can pass a version of the Context struct that fits. This doesn't get rid of most backwards compatibility problems, but you keep the Context struct clean by effectively having multiple structs in the kernel, one for each major / minor version.