Re: Hidden-code flaw in Windows renews worries over stealthly malware "Whoever" <nobody@devnull.none> wrote in message
news:Pine.LNX.4.63.0509022256350.27348@localhost.l ocaldomain...
> On Sat, 3 Sep 2005, Hairy One Kenobi wrote:
<snip>
> > LMAO on that one - VI is a perfectly reasonable line editor (first used
'em
> > on Cyber mainframes), but a fairly poor excuse for the FSEs that emerged
in
> > the 1980s.
>
> LMAO on that one. "ed" is the line editor, "vi" is the full screen editor.
Take a closer look at the command structure... an FSE doesn't require a
keypress to (say) change a character in the display.
That makes it - as I said - a poor excuse for an FSE coded in th last
quarter-century. EVE (an FSE sitting on top of EDT) showed how to do it
/properly/...
> Anyway, back to the original comment about the registry vs. config files:
> yes some config files for *nix applications are complex, however, many are
> quite simple and most contain detailed comments. I don't recall any
> comments in the registry....
Because an end user is supposed to be using the configuration tool, rather
than low-level editing? In the sixties and seventies, use of multiple config
files, shotgunned over every device on a system, was the norm. The registry
concept merged all of this into a single location - older versions of
Windows were just as guilty as everyone else at peppering your disks with
hard-to-find, hard-to-backup files.
Can't see what all the fuss is about.. unless you would care to argue about
piss-poor use of which sections in the registry bad developers tend to use?
Requiring admin rights?
H1K |