From: Aharon Robbins <arnold@skeeve.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] UN to fund linux for the 3rd world
Date: Thu, 2 Sep 2004 13:37:10 +0300 [thread overview]
Message-ID: <200409021037.i82AbApA009066@skeeve.com> (raw)
Lucio,
> > Quite seriously, why is *BSD "superior" to Linux? How do you define
> > "superior"? I would really like to know. (Let's take it as granted
> > that OpenBSD is more "secure". Fine. What other criteria are there?)
>
> That's not how I interpret the snippet you replied to. The "superior"
> platform would be Plan 9, the *BSD are mere alternatives to Linux.
I can see that - I admit it wasn't clear in the original post.
> Plan 9 is unquestionably superior, no quotes required.
Agreed.
> Firstly, there is no such thing as "full featured". For all of 10000
> packages (I'm guessing, but I think I'm pretty close) that NetBSD
> offers, I still can't conveniently exchange a PowerPoint presentation
> with a near infinite number of MS users unless I run some version of
> Windows. The same is valid even more for Visio (have I got the right
> name?). That is "full featured" even though Windows is lacking many
> of the options (ethereal, say) of the Unix world.
Full-featured is in the eye of the beholder (like most things); as
I expanded, I meant it as "lots of really useful programs already there
out of the box."
> Stable? Linux is considerably less stable than the *BSDs, as it is
> all too frequently updated.
I should have stated my definition. I meant "stable" as in "never crashes
unless the hardware is flakey." I do see your point using your definition,
and thus that's one point of the kind I was looking for in favor of *BSD.
> > The *only* issue I ever have with Linux is hardware support for either
> > very new or very proprietary hardware (monitors, network and video cards),
> > and that is usually solved with time. The installation experience has
> > only gotten *better* over the years.
>
> This weakness is a poor criticism to level at any OS competing with
> Windows.
It wasn't meant negatively; it was a statement of fact that, like it
or not, is a down point for Linux. It does apply to all non-MS OS's,
true.
I live in Israel. I can't just mosey on down to my local Circuit City
and pick out hardware that'll work with Linux. I have a good relationship
with a wonderful computer store, but they have hardware that they like.
In the past, I've had monitor/video card/sound card issues, which were usually
solved by the next linux release. More recently I had a wireless networking
card issue, where the box said "Linux" but it was a binary driver that
would only work for RH 9, not Fedora. (Solved via linuxant.com, but
that's another story.)
I guess what I'm trying to say is that overall, my experience has been
positive, but not picture perfect. That's OK.
> And, yes, I do appreciate that the
> Linux developers are leading in this race, but that's through sheer
> number, the *BSD device drivers are almost without fail better
> designed and implemented than the Linux ones they admittedly imitate.
Point two in favor of *BSD.
> So the question is not what ought to be recommended for the average user,
I was asking for me personally, as a committed techy/Unix type. I wasn't
out to solve the world's problems. :-)
> We also understand that without a much larger developers community,
> Plan 9 will stagnate, so we all pray that our favourite toy would
> become more widespread. But in my opinion it's another chimera, we
> need to attract more sophisticated developers, keep the quality of the
> system up, be less concerned about quantity. As long as Plan 9 can
> uniquely claim features such as a bullet-proof security, factotum,
> venti, uniformity of the namespace etc., it stands a head above the
> competitors. It may not have a popular following, but then if one is
> to judge by popular following, what can compete with Windows? And,
> for that matter, who would want to?
Well said.
Thanks,
Arnold
next reply other threads:[~2004-09-02 10:37 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 10:37 Aharon Robbins [this message]
2004-09-02 11:10 ` lucio
2004-09-02 18:54 ` dvd
2004-09-02 19:20 ` Boris Maryshev
2004-09-02 21:40 ` Charles Forsyth
2004-09-02 21:55 ` Boris Maryshev
2004-09-03 5:20 ` dvd
2004-09-03 6:22 ` lucio
2004-09-03 7:49 ` Charles Forsyth
2004-09-03 17:48 ` Jack Johnson
2004-09-03 17:52 ` ron minnich
2004-09-03 18:22 ` dvd
[not found] <Pine.LNX.4.44.0409031316170.22793-100000@maxroach.lanl.gov>
2004-09-03 19:53 ` Charles Forsyth
2004-09-03 21:11 ` dvd
2004-09-03 20:48 ` dvd
2004-09-03 20:52 ` ron minnich
2004-09-03 21:15 ` dvd
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 9:40 Aharon Robbins
2004-09-02 9:44 ` Dick Davies
2004-09-02 10:11 ` lucio
2004-09-02 10:52 ` George Michaelson
2004-09-02 11:21 ` lucio
2004-09-02 18:32 ` Jack Johnson
2004-09-02 22:58 ` Adrian Tritschler
2004-09-02 15:11 ` Sam
2004-09-02 19:51 ` boyd, rounin
2004-09-02 22:06 ` geoff
2004-09-03 2:33 ` Dan Cross
2004-09-01 14:48 boyd, rounin
2004-09-01 17:57 ` Jack Johnson
2004-09-01 17:59 ` boyd, rounin
2004-09-01 20:39 ` Tim Newsham
2004-09-01 21:16 ` boyd, rounin
2004-09-01 21:45 ` C H Forsyth
2004-09-02 3:24 ` Dan Cross
2004-09-02 3:31 ` George Michaelson
2004-09-02 4:24 ` Dan Cross
2004-09-02 5:15 ` Jeff Sickel
2004-09-02 5:38 ` andrey mirtchovski
2004-09-02 6:24 ` Zigor Salvador
2004-09-03 2:10 ` Dan Cross
2004-09-02 19:27 ` boyd, rounin
2004-09-02 20:38 ` Charles Forsyth
2004-09-02 22:44 ` Adrian Tritschler
2004-09-03 3:00 ` Dan Cross
2004-09-03 3:01 ` boyd, rounin
2004-09-02 5:03 ` Skip Tavakkolian
2004-09-02 5:13 ` George Michaelson
2004-09-02 9:10 ` Dick Davies
2004-09-03 2:13 ` Dan Cross
2004-09-03 2:38 ` George Michaelson
2004-09-05 0:30 ` Dick Davies
2004-09-05 0:31 ` boyd, rounin
2004-09-05 1:11 ` Jack Johnson
2004-09-05 2:50 ` boyd, rounin
2004-09-02 14:26 ` ron minnich
2004-09-02 21:48 ` Wes Kussmaul
2004-09-02 22:09 ` andrey mirtchovski
2004-09-03 0:21 ` Wes Kussmaul
2004-09-03 0:40 ` andrey mirtchovski
2004-09-03 4:39 ` Jack Johnson
2004-09-03 2:53 ` Dan Cross
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=200409021037.i82AbApA009066@skeeve.com \
--to=arnold@skeeve.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).