[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The future of NetBSD
- To: "Marco Peereboom" <slash_(_at_)_peereboom_(_dot_)_us>
- Subject: Re: The future of NetBSD
- From: "Constantine A. Murenin" <mureninc_(_at_)_gmail_(_dot_)_com>
- Date: Sat, 9 Sep 2006 19:19:42 -0400
- Cc: netbsd-users_(_at_)_netbsd_(_dot_)_org, misc_(_at_)_openbsd_(_dot_)_org, "Marc G. Fournier" <scrappy_(_at_)_freebsd_(_dot_)_org>, freebsd-chat_(_at_)_freebsd_(_dot_)_org, miros-discuss_(_at_)_mirbsd_(_dot_)_org
On 05/09/06, Marco Peereboom <slash_(_at_)_peereboom_(_dot_)_us> wrote:
> I don't think that binary only drivers are well enough.
> Surely better than nothing but ...
No fucking way. No support is FAR FAR better than a blob. Yes, really!
Indeed! When something brakes, do you want it to continue to work as
if nothing has happened and lose your data silently, or do you want it
to give you some indication that it needs attention?
* With binary drivers, it's always broken (and if it's not, it's
guaranteed to be broken in the future), but some people tend to
[foolishly] think that it's working.
* With drivers written from proper documentation by developers who
know their OS, it just works.
BTW, I'd argue that the same principle applies to the
manufacturer-supplied drivers for closed-source operating systems like
Windows -- it's better to have the drivers written by people who know
the OS it's written under, not by some random people hired by the
company that produced the hardware (which would never be the same
people who designed the hardware anyway, because people who design
hardware don't usually write software for it, and vice-versa).
freebsd-chat_(_at_)_freebsd_(_dot_)_org mailing list
To unsubscribe, send any mail to "freebsd-chat-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org