Likewise. TBH this has all been done with NewtonOS: http://preserve.mactech.com/articles/mactech/Vol.09/09.11/NewtonToolkit/index.html http://preserve.mactech.c

Likewise. TBH this has all been done with NewtonOS: http://preserve.mactech.com/articles/mactech/Vol.09/09.11/NewtonToolkit/index.html http://preserve.mactech.com/articles/mactech/Vol.09/09.11/Ne... It uses soup unions to manage removable storage, and worked really well for the 512k memory available. These days I'd recommend an embedded SQLite database for program configuration and data - somewhat standard, easily recoverable, backups are easy, uniform access from a program's API etc. Lastly, I'd say the ultimate OS would have a bit more than this surely - minimal formally verified TCB, Arrow datastructures, Managed (but not GC'd) memory, native scripting language that blurs the distinction between users and developers, fully scalable auto-generative but skinnable UI, just to name a few. I guess the trick with all of this is a suitable language which forms the OS base (think LISP OSes, Micropython, Squeak, AOS, NewtonOS), you get that correct and the rest can be layered on top.