From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 081F113838B for ; Mon, 22 Sep 2014 20:07:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DCC44E0AEB; Mon, 22 Sep 2014 20:07:39 +0000 (UTC) Received: from resqmta-po-01v.sys.comcast.net (resqmta-po-01v.sys.comcast.net [96.114.154.160]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 234D0E0AD4 for ; Mon, 22 Sep 2014 20:07:38 +0000 (UTC) Received: from resomta-po-04v.sys.comcast.net ([96.114.154.228]) by resqmta-po-01v.sys.comcast.net with comcast id uL6W1o0044vw8ds01L7eQK; Mon, 22 Sep 2014 20:07:38 +0000 Received: from ajax ([24.11.47.14]) by resomta-po-04v.sys.comcast.net with comcast id uL7d1o00H0JMh7c01L7d7a; Mon, 22 Sep 2014 20:07:38 +0000 Date: Mon, 22 Sep 2014 16:07:31 -0400 From: Frank Peters To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Boycott Systemd Message-Id: <20140922160731.4a2a4fddb0c965a11a911654@comcast.net> In-Reply-To: <20140922192438.GA27995@crud> References: <20140921143059.c3c16dfdeab6f65280b7caa6@comcast.net> <20140921192043.GA9652@crud> <20140921171301.5f008b3bd12c21c2f8fdd67e@comcast.net> <20140921202600.08d082d88014228172007477@comcast.net> <20140922175846.GA22399@crud> <20140922144114.3f89cd00fc13ce4a06515bce@comcast.net> <20140922192438.GA27995@crud> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.24; x86_64-unknown-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1411416458; bh=4RbzoVi96kM1OR4IWM/rjnbbdQrGLbAIAg/OOybbUvY=; h=Received:Received:Date:From:To:Subject:Message-Id:Mime-Version: Content-Type; b=PaiFbDRUktmfGxgujIKQrK8K6uGdLS7unoFYOXHF+ZQynBt4jyU5a3MqR6LY6FA6W 80+1H5PWSjsDZvGt4MpC4+gK84YONF+Xv6z417QVL7Uxgs3jRxLnMx7wz0X6Ss18b0 1C/IaY7cBDGcbih66ZZxXGTXVZ3OdtYr381n0bK54t15hPRyZEktpIA7X2c2cTLyoC eQSz1lVdOtXDvteiXRQAqsWrGkhANbRB//6uBTOhqVdQGqO4yG3tQLw7lYPYK/aey0 3VHwh/2ulMuMO3UuLFDBumPox5vm4n1PpUCaVeXrwDxXl39gwBbtQyqyBL5N2hU7qr Xm8ji6TPxUirA== X-Archives-Salt: 81c5392d-d1c6-4ab1-9cd6-4e140db70432 X-Archives-Hash: 1fde61119e89ceb0f5c36bd426b36039 On Mon, 22 Sep 2014 14:24:39 -0500 Barry Schwartz 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.