Why re-write another 'version' of Linux in an interrupted language?
The idea came to me when I found I was having to develop embedded Linux systems just to host a single Python application. Its just seemed like overkill. There was more `system` than app and in an environment where CPU time, memory and storage are a premium; it seemed like there had to be a better way. The thought of just creating enough userland to start and run the Python apps I was delivering on embedded platforms seemed useful. In wondering 'if' I could do it, I thought even if I failed or it never was actuality used for anything 'Production' supporting I'd sure learn a lot about the guts of Linux as well as Python.
In short, I see its use in rapid development and deployment of embedded Python applications. Any of the Python system interfaces should be an easy port to any Linux system as well.
Why Python?
Being an 'interrupted' language the files that make up your application ARE your source files. Imagine a system where you can edit the source files of any of the applications or shell commands directly with your text editor without the need to compile them! Not only that, but they are written in a language that is easy to read and understand. I love to tinker, this is makes it easier.
If I can edit any piece of my system, can't it get messed it up horribly?
Of course, but the future designs plans to have systems to help preventing a typo in an edit from making the system un-bootable. The idea of having 2 instances of the OS on the same machine (sort of akin to the i5 A and B systems) at the same time has come up. You can only edit the side of the system you aren't running and can only sync them once the edit has been tested. Or all the critical system files are in a read-only partition that can only be mounted read-write at boot.
If you have other ideas, we'd love to hear them!
