Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965175AbVLOIx4 (ORCPT ); Thu, 15 Dec 2005 03:53:56 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965176AbVLOIx4 (ORCPT ); Thu, 15 Dec 2005 03:53:56 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:23447 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S965175AbVLOIx4 (ORCPT ); Thu, 15 Dec 2005 03:53:56 -0500 Subject: Re: Linux in a binary world... a doomsday scenario From: Arjan van de Ven To: Al Boldi Cc: Nick Piggin , Greg KH , linux-kernel@vger.kernel.org In-Reply-To: <200512151131.39216.a1426z@gawab.com> References: <200512150013.29549.a1426z@gawab.com> <200512150749.29064.a1426z@gawab.com> <43A0FE13.8010303@yahoo.com.au> <200512151131.39216.a1426z@gawab.com> Content-Type: text/plain Date: Thu, 15 Dec 2005 09:53:50 +0100 Message-Id: <1134636830.16486.13.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-Spam-Score: -2.8 (--) X-Spam-Report: SpamAssassin version 3.0.4 on pentafluge.infradead.org summary: Content analysis details: (-2.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.8 ALL_TRUSTED Did not pass through any untrusted hosts X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1984 Lines: 54 > > Anyone else is free to fork the kernel and develop their own > > stable API for it. > > That would be sad. > > The objective of a stable API would be to aid the collective effort and not > to divide it. I think you missed how linux development works. Things fork all the time. The unsuccessful forks die. The successful ones join the "main line" again. Darwinism at work. You're free to put your coding where your mouth is and design and implement a stable API. If it's a success.. it'll get there. If it's not.. no harm done to the rest. > If you are working alone a stable API would be overkill. But GNU/Linux is a > collective effort, where stability is paramount to aid scalability. > > I hope the concepts here are clear. I think I don't get how you come from "stable API" to "aid scalability" in the light that the current non-API doesn't seem to prevent scalability to the size linux development is today. > > I've got a fairly good idea of what work I'm doing, and what I'm planning > > to do, long term goals, projects, etc. What would be the key differences > > with "non-GNU/OpenSource" development that would make you say they are not > > unguided by nature? > > The same goes for OpenSource in general, but GNU/OpenSource has a larger > community and therefore is in greater need of a stable API. again you skip a step. I see how a "large community" leads to "needs a visible API". The leap to "need stable API" I don't see in practice. > Arjan van de Ven wrote: > > I think Linux proves you wrong (and a bit of a troll to be honest ;) > > No troll! Just being IMHO. I hope that's OK? I hope you're also willing to put your effort where your words are, otherwise you are trolling to a large degree. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/