from lab book January 2007
Since the inception of a computer there has been many iterations of operating systems (os). Architectures were based on different requirements, platforms and goals. We have traversed back and forth on design, use and operation. Still the definition of an os is ambiguous at best.
myOS operating system design theory states all that is needed nothing more. This theory takes a minimalistic approach to os design. It separates core functions from applications; internal v.s. external processes. This is the approach that is the most efficient for the appliance based model or task specific servers. It promotes low overhead, high throughput and lacks the general dependency issues associated with a monolithic design. However, although as efficient, the minimalist approach is a difficult os to construct, upgrade and maintain. It takes a tremendous amount of knowledge and experience; it is not for the average os hacker.
The monolithic design approach includes a set of applications that clearly are part of the external processes. The advantages to the monolithic design is in theory; that all the included applications will be in sync and designed to complement each other. The reality of the process has become cumbersome and complicated for application developers to build applications to work in this environment. The applications included in this os design tend to work acceptably. However, third party applications suffer when they try to integrate and thus create interoperability issues.