Linked by Thom Holwerda on Wed 8th Mar 2006 22:57 UTC, submitted by hidden player
OSNews, Generic OSes Even a small operating system can have big disputes within its community. The lead developer of MenuetOS, an OS written in assembly, has decided to drop all support for the 32bit version of Menuet, focusing development on the 64bit version. However, disgruntled users of the open source operating system are trying to keep the 32bit version alive by starting a special forum for it.
Thread beginning with comment 102736
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Responsive
by transputer_guy on Thu 9th Mar 2006 06:54 UTC in reply to "RE: Responsive"
Member since:

I would have to agree with this and the 1st poster to mention it as well. Anyone who has been around long enough has already been there done that.

The project sounds interesting & I will follow it more, but the programming definitely takes me back to 1984 and the Inside Mac programming model where some coders such as Andy H could crank out all their apps in 68K asm because the early MacOS was so elegantly thought out (despite the memory handles & coop tasking handicaps).

In those days of tiny asm programming either x86 or 68K, it was well worth doing because every instruction performed in time in a predictable way. You could count clocks, bytes and choose which hand optimization would give better results even unrolling and inlining huge chunks of code. C to asm often gave 10x improvements.

Today that makes no sense and hasn't since the PPro and similar super scaler, out of order cpus made cycle counting irrelevant.

If Menuet has any interesting internals it should be programmed in a higher level language, perhaps BCPL or Lisp or just plain C. Dealing with asm codes isn't going to produce any applications more interesting than those 1984 apps. Which makes me wonder was the browser with the OSNews picture a native browser in asm too?

Interpreters are still a good idea provided the language and infrastructure are well designed, the user is still the limiting factor in keeping any OS busy. Today few books are available for modern x86 coding that can give a predicable model for how the code will actually run. There is a huge problem with the memory wall and true random access across large address spaces makes some "mov" instructions effectively 100s of cycles rather than 1 or so.

Reply Parent Score: 5