Computer Old Farts Forum
 help / color / mirror / Atom feed
Subject: [COFF] [TUHS] Isaacson v Unix [really RMS bashing]
Date: Wed, 09 Jan 2019 17:01:12 -0600	[thread overview]
Message-ID: <d9672e79451d6cc6582f04403b5c8df3@bitmessage.ch> (raw)
In-Reply-To: <201901062341.x06NfXe2021557@darkstar.fourwinds.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1375 bytes --]

Since y'all started it...

1. Close to 100% of gah-noo projects violate the Unix philosophy, the
Worse is better philosophy, the KISS principle, minimalist philosophies
etc.  Take just about any of the ``core'' projects, like glibc, as an
example, starting with getopt_long, which lets a developer create
PowerShell-like-named arguments, that are ``human readable''; and
ending with its static linking abilities, which needs no further
ranting.  It is in addition to the lead developer's attitude.

2. Close to 100% of GNU projects that simulate classic Unix utilities
introduce GNU'isms, one of them being already presented in the previous
point.  Sometimes it goes very far, so we cannot call the Linux kernel
as being written in C, but rather the ``GCC C'' dialect.
The musl and Clang projects demonstrate how much it takes to being able
to replace the respective components while maintaining compatibility.

3. GNU has never been about quality.  In fact, the aforementioned GCC
and glibc let developers write more and more bad code.

4. GNU and FSF have never been technical movements, they are political
movements that serve the interests of rms, and should be called as
such.

There are other projects that you all know and they don't need
additional ranting: GRUB, info, Autohell, GTK+, GNOME, and on top of
this, GPL.  (HURD is a joke, so not included).


--
caóc



           reply	other threads:[~2019-01-09 23:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <201901062341.x06NfXe2021557@darkstar.fourwinds.com>]

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=d9672e79451d6cc6582f04403b5c8df3@bitmessage.ch \
    --to=coff@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).