From: Frank Peters <frank.peters@comcast.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Boycott Systemd
Date: Mon, 22 Sep 2014 16:07:31 -0400 [thread overview]
Message-ID: <20140922160731.4a2a4fddb0c965a11a911654@comcast.net> (raw)
In-Reply-To: <20140922192438.GA27995@crud>
On Mon, 22 Sep 2014 14:24:39 -0500
Barry Schwartz <chemoelectric@chemoelectric.org> wrote:
> >
> > Someone has to write an apocalyptic novel about Linus Torvalds being
> > assassinated and his role taken over by the evil figures from ???.
>
> I’m simply concerned that one day he will retire.
>
We are now going into a completely different area.
But to proceed we have to understand the psychology which underlies
open source development.
In open source, ideally, there is no money involved. (I ignore
those who are on some corporate payroll.) What then is the motivation
to produce and develop open source software?
It is EGO which drives open source. Let there be no denying. Open
source developers obtain their primary satisfaction by showing off
their programming prowess. They want to be well known and famous
for their programming achievements.
When Torvalds steps out of the picture, for whatever reason, the
void will be filled by ego maniacs who want to claim the title
of Prime Linux Guru. Linus is Top Dog Numero Uno now, but we
can imagine that all his subordinates eagerly crave his status
and there will be great contention among them to be enthroned
in his place when he is gone.
I predict, if this were to happen, that Linux would transform into
the personal toy of its egotistical developers.
Of course, we would also have to anticipate the gabbing (or buying)
of Linux by big corporate interests. In this case, the market forces
surrounding the "lowest common denominator" would be the guiding
principle of development.
In either case we would have degeneration.
>
> We cannot rely on the programming community to do the right thing. We
> are, for instance, sticking canaries on the stack while continuing to
> write crucial software like OpenSSL entirely in languages that
> _guarantee_ buffer overruns; and the programmer will continue to be
> blamed, instead of the practices. (Those who care may want to check
> out www.ats-lang.org for a practical alternative to C, suitable even
> for writing kernel modules.)
>
How difficult would it be to introduce bounds checking on all
C arrays as with some other languages? Would bounds checking
reduce the efficiency and speed of C, as these are probably
its most desired characteristics? C is essentially only one
small step away from machine language and that's why it's
preferred for systems programming.
next prev parent reply other threads:[~2014-09-22 20:07 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 17:25 [gentoo-amd64] Boycott Systemd Frank Peters
2014-09-21 17:37 ` Canek Peláez Valdés
2014-09-21 18:30 ` Frank Peters
2014-09-21 19:15 ` Canek Peláez Valdés
2014-09-21 19:20 ` Barry Schwartz
2014-09-21 19:22 ` Canek Peláez Valdés
2014-09-21 19:33 ` Barry Schwartz
2014-09-21 19:45 ` Canek Peláez Valdés
2014-09-21 19:48 ` Canek Peláez Valdés
2014-09-21 21:13 ` Frank Peters
2014-09-21 22:04 ` Canek Peláez Valdés
2014-09-21 22:15 ` Harry Holt
2014-09-21 22:28 ` Canek Peláez Valdés
2014-09-22 5:27 ` [gentoo-amd64] " Duncan
2014-09-22 0:26 ` [gentoo-amd64] " Frank Peters
2014-09-22 0:45 ` Rich Freeman
2014-09-22 2:02 ` Frank Peters
2014-09-22 2:34 ` Rich Freeman
2014-09-22 6:00 ` [gentoo-amd64] " Duncan
2014-09-22 12:47 ` Harry Holt
2014-09-22 12:53 ` Rich Freeman
2014-09-22 16:14 ` Duncan
2014-09-23 14:55 ` Frank Peters
2014-09-24 11:25 ` Duncan
2014-09-24 16:58 ` Frank Peters
2014-09-25 4:12 ` Duncan
2014-09-25 11:34 ` Harry Holt
2014-10-07 14:18 ` Harry Holt
2014-10-07 14:55 ` Barry Schwartz
2014-10-07 17:04 ` Rich Freeman
2014-10-07 20:43 ` Barry Schwartz
2014-10-07 20:54 ` Damien Levac
2014-10-07 21:19 ` Barry Schwartz
2014-10-07 21:45 ` Rich Freeman
2014-10-08 1:15 ` Frank Peters
2014-10-08 2:28 ` Rich Freeman
2014-10-08 3:19 ` Harry Holt
2014-10-08 12:34 ` Phil Turmel
2014-10-08 18:02 ` Frank Peters
2014-10-08 21:42 ` Barry Schwartz
2014-10-08 3:23 ` Frank Peters
2014-09-22 13:23 ` Barry Schwartz
2014-09-22 17:00 ` Frank Peters
2014-09-22 16:21 ` Frank Peters
2014-09-22 19:46 ` Duncan
2014-09-22 17:04 ` [gentoo-amd64] " Lie Ryan
2014-09-22 17:58 ` Barry Schwartz
2014-09-22 18:22 ` Canek Peláez Valdés
2014-09-22 19:08 ` Barry Schwartz
2014-09-22 19:18 ` Canek Peláez Valdés
2014-09-22 19:46 ` Barry Schwartz
2014-09-22 19:30 ` Frank Peters
2014-09-22 19:37 ` Rich Freeman
2014-09-22 19:39 ` Canek Peláez Valdés
2014-09-22 19:54 ` Barry Schwartz
2014-09-22 20:08 ` Harry Holt
2014-09-22 20:22 ` Canek Peláez Valdés
2014-09-23 4:00 ` Canek Peláez Valdés
2014-09-23 3:51 ` Antoine Martin
2014-09-23 4:07 ` Barry Schwartz
2014-09-23 5:17 ` [gentoo-amd64] grub2 upgrade fail (was Boycott Systemd) Antoine Martin
2014-09-23 5:42 ` Barry Schwartz
2014-09-23 5:50 ` Barry Schwartz
2014-09-24 12:29 ` [gentoo-amd64] " Duncan
2014-09-23 4:09 ` [gentoo-amd64] Boycott Systemd Canek Peláez Valdés
2014-09-23 4:32 ` Barry Schwartz
2014-09-23 4:48 ` Canek Peláez Valdés
2014-09-23 5:49 ` Frank Peters
2014-09-23 6:05 ` Barry Schwartz
2014-09-23 6:31 ` Canek Peláez Valdés
2014-09-23 5:28 ` Barry Schwartz
2014-09-23 17:11 ` Paul Jewell
2014-09-23 23:31 ` Systemd is really beside the point, anyway (was Re: [gentoo-amd64] Boycott Systemd) Barry Schwartz
2014-09-24 12:45 ` [gentoo-amd64] Re: Boycott Systemd Duncan
2014-09-22 18:41 ` [gentoo-amd64] " Frank Peters
2014-09-22 18:44 ` Canek Peláez Valdés
2014-09-22 19:24 ` Barry Schwartz
2014-09-22 20:07 ` Frank Peters [this message]
2014-09-22 20:24 ` Barry Schwartz
2014-09-22 20:24 ` [gentoo-amd64] " Duncan
2014-09-22 18:07 ` [gentoo-amd64] " Frank Peters
2014-09-22 16:11 ` Lie Ryan
2014-09-22 16:35 ` Barry Schwartz
2014-09-22 17:55 ` Frank Peters
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=20140922160731.4a2a4fddb0c965a11a911654@comcast.net \
--to=frank.peters@comcast.net \
--cc=gentoo-amd64@lists.gentoo.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