From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262161AbTJ3Bea (ORCPT ); Wed, 29 Oct 2003 20:34:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262164AbTJ3Bea (ORCPT ); Wed, 29 Oct 2003 20:34:30 -0500 Received: from h1ab.lcom.net ([216.51.237.171]:13187 "EHLO digitasaru.net") by vger.kernel.org with ESMTP id S262161AbTJ3Be2 (ORCPT ); Wed, 29 Oct 2003 20:34:28 -0500 Date: Wed, 29 Oct 2003 19:34:19 -0600 From: Joseph Pingenot To: Neil Brown , Dax Kelson , Hans Reiser , andersen@codepoet.org, linux-kernel@vger.kernel.org Subject: Re: Things that Longhorn seems to be doing right Message-ID: <20031030013418.GD3094@digitasaru.net> Reply-To: trelane@digitasaru.net Mail-Followup-To: Neil Brown , Dax Kelson , Hans Reiser , andersen@codepoet.org, linux-kernel@vger.kernel.org References: <3F9F7F66.9060008@namesys.com> <20031029224230.GA32463@codepoet.org> <3FA0475E.2070907@namesys.com> <1067466349.3077.274.camel@mentor.gurulabs.com> <20031030002005.GC3094@digitasaru.net> <16288.24913.844699.956689@notabene.cse.unsw.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16288.24913.844699.956689@notabene.cse.unsw.edu.au> X-School: University of Iowa X-vi-or-emacs: vi *and* emacs! X-MSMail-Priority: High X-Priority: 1 (Highest) X-MS-TNEF-Correlator: X-MimeOLE: Not Produced By Microsoft MimeOLE V5.50.4522.1200 User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>From Neil Brown on Thursday, 30 October, 2003: >On Wednesday October 29, trelane@digitasaru.net wrote: >> Regardless, it's an interesting idea, and one which might be fruitful. >> I give you then two bits: our treatment of the tech and the reality of their >> tech: >> 00: ISVAPOR | TAKESEROUSLY >> 01: ISVAPOR | IGNORE >> 10: NOTVAPOR | TAKESERIOUSLY >> 11: NOTVAPOR | IGNORE >> If we come up with a working implementation and it *is* just vaporware, then >> we're ahead. >> We're way ahead. >> If we merely dismiss it as vaporware and it turns out to be, >> no net change. >...snip... >> Conclusion: best to take it seriously and work on it; those two cases >> are the most optimal. >Sounds like the same argument that is used in "Pascal's Wager" for >belief in God, and I seriously don't think the argument works in >either case. (note that I'm not making a statement about the >conclusion in either case, only about the arguement). "Sounds like?" Sure. It kind of does, now that you mention it. Regradless of the similarities and the validity of Pascal's argument, my argument, I think, stands. I outlined the four potential futures. We have control over only one bit, Microsoft has the other. The tech sounds nice, it is an interesting avenue to persue, Pascal aside. I don't see any reason why we *shouldn't* look at the problem and try to do it. What reasons do you see for not persuing the problem to its inevitible implementation? I see big pitfalls in *not* looking at the problem. In what respect are the pitfalls of ignoring it as outlined by me invalid? mfG, Joseph -- Joseph===============================================trelane@digitasaru.net "Asked by CollabNet CTO Brian Behlendorf whether Microsoft will enforce its patents against open source projects, Mundie replied, 'Yes, absolutely.' An audience member pointed out that many open source projects aren't funded and so can't afford legal representation to rival Microsoft's. 'Oh well,' said Mundie. 'Get your money, and let's go to court.' Microsoft's patents only defensive? http://swpat.ffii.org/players/microsoft