home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!newsfeed.rice.edu!uw-beaver!cs.ubc.ca!unixg.ubc.ca!kakwa.ucs.ualberta.ca!acs.ucalgary.ca!cpsc.ucalgary.ca!debug!castrov!kgwcal!ken
- From: ken@kgwcal.UUCP (Ken Wiens)
- Newsgroups: comp.os.os2.advocacy
- Subject: Re: The sin of MicroSoft
- Distribution: world
- Message-ID: <726732945snx@kgwcal.UUCP>
- References: <1ippcdINNadq@tamsun.tamu.edu>
- Date: Mon, 11 Jan 93 06:15:45 GMT
- Organization: Ken Wiens Consulting
- Lines: 41
-
- > |My opinion on why so much has been focused on GUIs is that multitasking is
- > |not as important without a GUI. Case in point, Unix has had multitasking
- > |abilities for years--but unless one was a programmer, programs were more
- > |or less run "serially"; and multitasking was basically used by a novice
- > |user (if one could say Unix _had_ any novice users) for drudgery such as
- > |pipes or servers... PEOPLE didn't multitask with computers, PROGRAMS did.
- >
- > I tend to agree with you here, but people did multi-task implicitly
- > under unix. If a program did A|B|C A, B, and C were run
- > concurrently. This type of behavior gets output to the user a lot
- > sooner than the DOS method of creating intermediate scratch files and
- > running the programs sequentially. You didn't need to be a programmer
- > to do this, but I agree that the skill level of the operators was
- > quite a bit higher than the average GUI user.
-
- Users of SCO unix or Xenix, explicity multitasked whenever they utilized the
- multiscreen function. It acted like multiple windows (except that each window
- was a full screen). IMHO the only advantage of the GUI is a nice way to select
- among multiple tasks. The main difference between SCO's multiscreens and
- windows, is that changing among multiscreens was typically extremely fast
- (ie immediate -even on a '286) while changing among windows, can be rather
- painful without fairly up to date hardware. The points are:
-
- 1. You can multitask without having to be graphical to select among the tasks, and
-
-
- 2. novice users can easily make use of this capability.
-
-
- ****************************************************************************
- * Ken Wiens * *
- * Ernst & Young * Using OS/2 and UUPC/extended *
- * Calgary, Alberta, Canada * *
- * * *
- * via ken@kgwcal.uucp * *
- * voice 403-251-2980 * *
- ****************************************************************************
- * *
- * ack - A signal indicating that the error-detection circuits have failed *
- * *
- ****************************************************************************
-