delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2004/01/10/03:48:19

X-Authentication-Warning: delorie.com: mail set sender to opendos-bounces using -f
Sender: day AT delorie DOT com
Message-ID: <3FFFD7F6.393BD45@hypertech.net>
Date: Sat, 10 Jan 2004 02:46:14 -0800
From: Day Brown <daybrown AT hypertech DOT net>
X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.16 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: opendos AT delorie DOT com
Subject: Re: FreeDos, twenty four years later...
References: <20040108231511 DOT 17912 DOT qmail AT web40703 DOT mail DOT yahoo DOT com> <3FFF0297 DOT 8730 DOT 301E8FD AT localhost>
Reply-To: opendos AT delorie DOT com

shadow AT shadowgard DOT com wrote:
 
> > The main reason I subscribe to the OpenDOS
> > newsgroup is that, for me, the old DOS was both easy to learn and also
> > very *simple* to manage. One only has to play around with one of the
> > current flavours of UNIX/Linux for, say, twenty minutes, before one
> > realizes one isn't in Kansas anymore. UNIX makes some very simple things
> > a lot more complicated!
> 
> Oh?
Linux is simple enough if you're satisfied with what the distro you have
offers. But trying to add or change anything can lead to endless threads
such as we see in the Linux lists. The unintended consequences are
considerably larger because Linux has so much more power.
 
> > I'm not a psychic, but if Gary Kildall was alive today, I suspect he'd
> > have taken our OpenDOS to new territories. Unfortunately, he is no
> > longer with us so we will have to imagine what kind of operating system
> > he would now be showing us (probably a hybrid of DOS, Netware,
> > DESQview/X, and EOS). As for computer languages, maybe we should follow
> > UNIX and simply standardize on plain C?
> 
> C is a problem language. It tends to encourage
> certain *bad* programming practices. Like unchecked
> type casting.
I never cared for it either. In dos, anything you want to do has already
been written, and if not, you'll ed up using batch and/or assy to solve
the problem.

Why dont the print screen key work in Linux? cause it was designed by
and for system administrators, who dont need a hard copy nearly as often
as the home user, who has his printer next to him, whereas a network
printer can be anywhere on earth. Linux is terrific for business, with
very stable networks the users cannot screw up. But home users get
annoyed being told they dont have 'permission'.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019