Yeah, I might be just re-inventing the wheel here, who knows? But I had this (original? I doubt it) idea a few months ago and I was meant to write about it for some time now. So, my idea is about creating a new operating system that is like none of the current ones. It would be so different, that porting applications from other "traditional" systems wouldn't be possible. But the gains would be much more important of what we would lose by implementing a brand new new system.
Permalink for comment
To read all comments associated with this story, please click here.
Eugenias OS approach proposal doesn't, afaik, prevent you from designing an app that LOOKS and ACTS like Photoshop.
Say you're building Photoshop in this environment. You start by sketching some on what functions and routines you will need in your application. When you have an idea you make use of as many modules as you can. Some modules may not be advanced enough - then you write a extension module to them. Some may not exist - then you write them. When you're done with all the core functions needed by the modules you can start designing the "app itself", which in this case only need to be a framework to connect all the modules and call the right modules in the right time. It isn't really that revolutionary, just one step further than existing solutions like ie KParts.
The point of writing a new OS for this is that a traditional OS is written for tradidional monolitic applications to be able to run well on top of the kernel. Alot of this traditional functions in kernel communication with userland could be cut. Cleanest, and probably easiest in the long run, would be to have a kernel specialized on this.
If OBOS plays their cards right they might have the answer to this OS request one day. If not, I'm sure someone else will. Time will tell.
Eugenias OS approach proposal doesn't, afaik, prevent you from designing an app that LOOKS and ACTS like Photoshop.
Say you're building Photoshop in this environment. You start by sketching some on what functions and routines you will need in your application. When you have an idea you make use of as many modules as you can. Some modules may not be advanced enough - then you write a extension module to them. Some may not exist - then you write them. When you're done with all the core functions needed by the modules you can start designing the "app itself", which in this case only need to be a framework to connect all the modules and call the right modules in the right time. It isn't really that revolutionary, just one step further than existing solutions like ie KParts.
The point of writing a new OS for this is that a traditional OS is written for tradidional monolitic applications to be able to run well on top of the kernel. Alot of this traditional functions in kernel communication with userland could be cut. Cleanest, and probably easiest in the long run, would be to have a kernel specialized on this.
If OBOS plays their cards right they might have the answer to this OS request one day. If not, I'm sure someone else will. Time will tell.