From owner-freebsd-chat@FreeBSD.ORG Tue Jun 10 23:57:13 2003 Return-Path: Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 462D737B401 for ; Tue, 10 Jun 2003 23:57:13 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7E0843FD7 for ; Tue, 10 Jun 2003 23:57:12 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0s4.dialup.mindspring.com ([209.86.3.132] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19PzXb-0004nX-00; Tue, 10 Jun 2003 23:57:04 -0700 Message-ID: <3EE6D267.98AFA614@mindspring.com> Date: Tue, 10 Jun 2003 23:55:35 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Rahul Siddharthan References: <20030610121303.A20545@online.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4e1f105c4d95ca15067bde2538977ef34667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: Craig Reyenga cc: freebsd-chat@freebsd.org Subject: Re: FreeBSD Version Release numbers X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2003 06:57:13 -0000 Rahul Siddharthan wrote: > Terry Lambert wrote: > > The problem with this is you are very soon running version 99 > > (or 100, if you want it stable). > ... > > Nothing can kill a product faster than version bloat; witness > > NetWare and Oracle. > > But MS Windows reached version 2000 some time back, and isn't dead yet. "That's not a version, that's a ship [date]". Windows is now smart enough to name things after ephemeral things that encourage upgrading. You'll notice NT never got to version 5. I've also observed that they have gotten away from attention grabbing failure indicators, and are now much more understated (it helps that they indicate the fault was in the application, rather than in the OS routine that the application called that didn't validity check its input parameters). -- Terry