posted by Desmond Ong on Tue 1st Jan 2002 22:43 UTC
IconWe hail those who attempt to create new operating systems from scratch. They are the leaders, the visionaries, the influencers of this great tech-age. There will always be only 2 areas of how an OS can be great - great marketing (which provides great third party support), and great design. Microsoft has always invested more in the former, and Apple in the latter. This article discusses some design aspects. Update: The article has been updated at several places.

Editorial notice: All opinions are those of the author and not necessarily those of osnews.com

The most important thing during a startup I believe, is to learn from the experts who have created great operating systems before. Like Mac OSX or BeOS.

Designing an OS for the masses is about creating that ultimate user experience. It is about designing something to increase workflow and productivity, without having the users fiddling around with the default settings just to get some tasks done. The masses are those who are afraid of a command-line interface (CLI), and if a Graphical User Interface (GUI) is designed with a CLI as a central core or generator for everything else, it is designed to fail in its mass appeal.

Although I'm primarily a Windows user, I believe I know why the Mac GUIs have such a long standing in their user friendliness. Many users who have had no prior computer experience have been captivated by the Mac GUI and stuck with it over the years despite the instability and sluggish performance. The secret to this success lies in the hiding of its CLI. The Mac OS designers have gone to great lengths to either eliminate the CLI (older Mac OS), or hide the CLI (Mac OSX). Microsoft knew from the start the importance of hiding the CLI (DOS) and "borrowed" the idea from Apple. Hiding the CLI meant that everything that could possibly be done should now be possible with the GUI. With this regard, Linux may never take off as a desktop OS, as long as the CLI is kept in the foreground, and that users would still have to grapple with it, even if it's a simple command.

Table of contents
  1. "Hiding the Command Line Interface"
  2. "Usabilty and Design Aesthetics"
  3. "The Default Interface"
  4. "Packaged Ability"
  5. "Speed, Power, Efficiency"
e p (0)    34 Comment(s)

Related Articles

posted by Kroc Camen on Thu 4th Dec 2008 18:20
posted by Thom Holwerda on Wed 12th Nov 2008 22:55
posted by Thom Holwerda on Sat 23rd Aug 2008 15:37