11226
Living Room / Re: which operating system you like most....
« Last post by 40hz on October 14, 2008, 08:58 PM »An "object-oriented OS" doesn't necessarily meant it's implemented an OOP language, but probably more along the lines of being modularized, and modules being interconnectable/scriptable (kinda like I understand Apple have been trying to do on OSX with "that scripting language" that is "pretty widely supported"?).
Also, you don't need a language with syntactic sugar to do OOP programming - people are doing it in C and Assembly probably without even knowing (as soon as you're dealing with the win32 API, you're doing OO programming, whether you realize it or not).
-f0dder (October 14, 2008, 07:03 PM)
I don't think of object-oriented design and modularization as being one and the same thing - although I could be wrong in my opinion. What you are describing sounds very much like something that has already been done. I'm referring to the concurrent development of the Modula-2 programming language and the Lilith Workstation back in 1978. These were actual working systems, not just some paper or wire-wrap prototypes. Here's a 1981 vintage unit in use. Looks a lot like another computer that came out in January of 1984 doesn't it?
From: A Brief History of Modula and Lilith
http://www.modulaware.com/mdlt52.htm
The need for a structured language with a module facility was less pronounced in the software community at large than in our immediate environment. An explanation of this requires some digression. The computing facilities available in 1977 were essentially large scale mainframes hosting sophisticated time-sharing systems, accessible only via terminals and remote satellites. The revolutionary concept of the powerful, personal workstation - the Alto computer developed at PARC - appeared to me like a revelation [4]. I was immediately convinced that there was no point in continuing development of software, except if based on and oriented towards this novel computing environment. However, such devices not being available on the market, there remained only one path to proceed, namely to design and build one on our own. Again, there was a recogized need and an idea of a solution. The project produced the workstation Lilith [5, 6].
There is no point in creating new hardware without new software. A basic operating system, utility programs, and first applications were to be developed concurrently, and therefore a programming language and its compiler were required as well. In fact, the primary incentive for designing Modula-2 was the need for a simple, allround language capable of expressing the whole range of programs needed to render Lilith into a powerful software development tool. The explicit goal was to use one and the same language for all Lilith software. Evidently, Modula and Lilith grew as a couple, and it would be futile to record the history of one without that of the other.***In December 1980, the first pilot series of 20 Liliths, manufactured in Utah under the supervision of R. Ohran, were delivered to ETH Zurich. Further software development proceeded with a more than a 20-fold hardware power at our disposal. A genuine personal workstation environment had successfully been established.
You can download the Lilith design spec (in PDF format) from here:
http://www.cfbsoftwa...les080813/Lilith.pdf
And the Modula-2 Handbook here:
http://www.cfbsoftwa...dula2%20Handbook.pdf
Modula-2 did not directly support object-oriented programming it was still possible to do it:
Although Modula does not support object-oriented programming, it at least makes it possible through the use of the type ADDRESS and the rule that an address value may be assigned to any pointer variable.
The Lilith Workstation and Modula-2 Programming language were succeeded by the Ceres workstation and the Oberon Programming Language. The Oberon OS is itself written in the Oberon programming language.

Recent Posts
).
Thanks, I guess... (yuck!)
