From: Brian Beattie <beattie@beattie-home.net>
To: linux-fsdevel@vger.kernel.org
Subject: Re: Controversial: A New FRUGAL File System? Linux Registry (again)?
Date: 29 Oct 2003 14:10:06 -0500 [thread overview]
Message-ID: <1067454607.4265.6.camel@kokopelli> (raw)
In-Reply-To: <OF222E7E68.487BFE89-ON88256DCD.0067F6DA-88256DCD.006A0F5A@us.ibm.com>
On Tue, 2003-10-28 at 14:18, Bryan Henderson wrote:
> >M$ tried this with *.ini files. They were text file friendly, but got
> unwieldy
> >pretty darn quick, when you started to automate other configuration data
> >in them. The same problem will progressively occur under Linux/UNIX
> >as software gets more complicated each year.
>
> The progression in the Windows world wasn't because software got more
> complicated -- it was because users got less sophisticated and more
> demanding. If Linux is to progress to where Windows is, then I agree that
> anything like .ini files has to go. But it would be wrong for Linux to
> progress to where Windows is. Windows is already there. In moving from
> .ini files to a registry, Windows moved ahead in certain areas and behind
> in others. Folks who benefitted from .ini files in DOS, then moved from
> Windows to Linux.
Please excuse me, I'm an old fart and remember the days even before ini
files, though never fooled much with MS software. I've always heard
that there was some problem with ini files, and that for this reason MS
went with the registry, but I was never too clear what the problem, I
sort of had the impression that it was lazy and incompetent Windows
programmers who could not manage their own configuration files, but
maybe that was just my own bias showing.
Can somebody tell be just what the problem with ini files was, that the
registry was supposed to solve?
--
Brian Beattie | Experienced kernel hacker/embedded systems
beattie@beattie-home.net | programmer, direct or contract, short or
www.beattie-home.net | long term, available immediately.
"Honor isn't about making the right choices.
It's about dealing with the consequences." -- Midori Koto
prev parent reply other threads:[~2003-10-29 19:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 0:14 Contraversial: A New FRUGAL File System? Linux Registry (again)? Warren W. Gay VE3WWG
2003-10-27 6:36 ` Charles Manning
2003-10-27 7:10 ` Joseph D. Wagner
2003-10-27 7:26 ` Charles Manning
2003-10-27 7:44 ` Joseph D. Wagner
2003-10-28 3:51 ` Warren W. Gay VE3WWG
2003-10-28 3:49 ` Warren W. Gay VE3WWG
2003-10-28 3:05 ` Warren W. Gay VE3WWG
2003-10-27 17:41 ` Controversial: " Bryan Henderson
2003-10-28 3:31 ` Warren W. Gay VE3WWG
2003-10-28 13:08 ` Ingo Oeser
2003-10-28 13:12 ` Matthew Wilcox
2003-10-28 16:06 ` Ian Kent
2003-10-28 19:18 ` Bryan Henderson
2003-10-29 19:10 ` Brian Beattie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1067454607.4265.6.camel@kokopelli \
--to=beattie@beattie-home.net \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox