From owner-freebsd-chat@FreeBSD.ORG Thu Apr 10 06:20:59 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 D50D137B401 for ; Thu, 10 Apr 2003 06:20:59 -0700 (PDT) Received: from net.wau.nl (net.wau.nl [137.224.10.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id C79A643F75 for ; Thu, 10 Apr 2003 06:20:58 -0700 (PDT) (envelope-from FST777@phreaker.net) Received: from asser079.athome239.wau.nl (asser079.athome239.wau.nl [137.224.239.79]) by net.WAU.NL (PMDF V5.2-32 #38746) with ESMTP id <0HD400JSPQEQKJ@net.WAU.NL> for chat@freebsd.org; Thu, 10 Apr 2003 15:20:50 +0200 (MET DST) Date: Thu, 10 Apr 2003 15:21:51 +0107 (CEST) From: "Frans-Jan v. Steenbeek" To: chat@freebsd.org Message-id: <0HD400JSQQEQKJ@net.WAU.NL> MIME-version: 1.0 X-Mailer: Spruce 0.6.5 for X11 w/smtpio 0.7.9 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 8BIT Subject: Re: .NET on FreeBSD X-BeenThere: freebsd-chat@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: FST777@phreaker.net List-Id: Non technical items related to the community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 13:21:00 -0000 I was kinda kidding, but serious: with the upcoming Palladium-technology (one of the reasons why I decided to look for a replacement for Window$ before get into the new stream of control comming up) I don't think it is a good idea to add .NET to, and develope .NET for FreeBSD, especially when it is only usefull for Open-Source applications. .NET is the first (or twenthieth or whatever) of series of Micro$ofts efforts to get control over the world market and to get a view of the way users use their PC. Palladium will be the next step and I think Micro$oft will make .NET fully Paladium-depended. I fear that when a .NET-implementation is added to the ports-collection of FreeBSD (and as a package for Linux or other Open-Source efforts) it will be used too much to develope cros-platform software. This will lead to the fact that even Open-Source users will then on the long term have to use this NET-implementation and become (again) under the control of Micro$ofts bugs. In other words, it may only tighten our freedom. On Wed, 09 Apr 2003, Chip Morton wrote: > Date: Wed, 09 Apr 2003 23:35:09 -0500 > To: FreeBSD Chat > From: Chip Morton > Subject: Re: .NET on FreeBSD > > In addition to the execution engine itself, the Shared Source CLI > include source code to practically every .NET tool that comes with the CLR (and > some that don't!) including complete C# and JScript® compilers and > portable versions of all the familiar .NET tools.... > I really think it could be very beneficial to FreeBSD (or any OS for that > matter) to have a fully functional .NET CLR environment. Not only would it > open up a load of Windows software developed to FreeBSD users, but it could > make FreeBSD a viable replacement for a Windows desktop or IIS server. In > other words, it could only broaden our market share.