Could .NET choke Windows?

James Pullicino

If the following two statements are true: .NET framework will replace the Windows API .NET framework can be ported to Linux Then what will be the role of Windows? James Drinking In The Sun Forgot Password?

Jeremy Pullicino

Well, today in the paper I read that 3 dolphins were choked when they got cought in a fisherman's .NET .... Maybe windows will suffer the same fate... jeremy.;P "Hey man, Taliban, Tali me Banana."

Tomasz Sowinski

The second statement is problematic. While parts of .NET are ported to Linux, there are substantial pieces which remain on Win32/64 (ASP.NET, ADO.NET, WinForms). Yes, I know about the company which provides ASP.NET on Apache, but it'll work on Apache-Win only. BTW: why are you so concerned about future of Windows? Tomasz Sowinski -- http://www.shooltz.com

- It's for protection
- Protection from what? Zee Germans?

Brian Azzopardi

You're implicitly assuming that the Windows API could not/has not been ported to Linux. Wine is one such port. All the windows ports never got very far. Porting .Net to Linux will not change anything in the large scheme of things. And who told you that .Net will be/can be ported to Linux. The Mono project has only ported the compiler and some other bits. Porting the whole .Net is a huge undertaking. It also brings up the issue of why should ppl chnage over to linux to run .Net when Windows is easier to use, comes with .Net built-in, is pretty reliable, and has 90% market share. No one ever got fired for choosing Windows. bibamus, edamus, cras moriemur

[eat, drink, for tomorrow we die]

jparsons

.NET framework can be ported to Linux This is already in the works with Mono. Porting .NET to another platform ( particularly Linux ) would hurt Java more than it would hurt Windows. Java has suffered on Windows due to the Legal battles between Sun and Microsoft. Now Developers would have a language not entangled in lawsuits which worked great on both platforms. .NET framework will replace the Windows API This is a litlte bit more unlikely. The .NET environment relies on the Windows API for lots of its functionality. .NET was designed to be architecture independent. As such there are certain API calls which are very Windows Specific which will never end up in the .NET framework API. So developers needing those calls will be forced to use PInvoke. Jared jparsons@jparsons.org www.prism.gatech.edu/~gte477n

James Pullicino

Tomasz Sowinski wrote: why are you so concerned about future of Windows? I'm curious not concerned ;) Drinking In The Sun Forgot Password?

Not Active

Brian Azzopardi wrote: Wine is one such port It's a Linux/Windows port? I thought it was a User request. But why can't I access the network, why can't I open the email attachment;P

Colin Leitner

I don't see any reason why .NET shouldn't be ported to another platform like linux. Many CLR classes are completely written in C# or VB.NET and when ildasm can access the raw code, why shouldn't developers be able to extract it? And there have been so many asm-emulators developed that writing one for .NET shouldn't be that hard. Brian Azzopardi wrote: Porting the whole .Net is a huge undertaking Right, but who said you need to port everything? All base classes you need really are the basic types. Everything else can then be written in C# (except the native stuff of course).

Brian Azzopardi

The windows API was ported to Linux too but did that convince people to drop Windows? Of course it should be ported. I'm not saying it shouldnt, I just don't see the point. Remember that the point of the thread is whether .Net will choke Windows because it might be ported to Linux and thus making Windows irrelevant. I can assure you that MS will do everything in its power (ask Netscape) to make sure that this does not happen. bibamus, edamus, cras moriemur

[eat, drink, for tomorrow we die]

Erik Westermann

Rotor[^] runs on FreeBSD. Here's a quote from the Rotor page: The Shared Source CLI goes beyond the printed specification of the ECMA standards, providing a working implementation for CLI developers to explore and understand. It will be of interest to academics and researchers wishing to teach and explore modern programming language concepts, and to .NET developers interested in how the technology works. I have tried it- really :cool: stuff! Erik Westermann Author, Learn XML In A Weekend (Fall 2002)

mstephens

Well if Microsoft does everything in it's power and makes .NET on Windows that much better than .NET on other platforms then that will probably be a good thing for .NET users on the Windows platform. Lets face it compared to IE Netscape is a load of crap

Ryan Johnston 0

Jeremy Pullicino wrote: I read that 3 dolphins were choked when they got cought in a fisherman's .NET Maybe it is a sign that some how .NET will bring about the end of MYSQL!

Colin Leitner

Brian Azzopardi wrote: The windows API was ported to Linux too but did that convince people to drop Windows? Yes, but installing and using wine is kind of hard (for a newbie linux user!) and other ports should have rather investated their time in wine instead of reinventing the wheel a hundred times. I think the main reason for a very large group of people not to use linux is the lack of Adobe products (mainly Photoshop), not the W32 API. Developers can build their own tools, but customers can't.

Ryan Johnston 0

Colin Leitner wrote: Yes, but installing and using wine is kind of hard (for a newbie linux user!) Which is probably the same thing that is going to keep .NET on Linux from taking off.

David Wulff

:)

David Wulff http://www.davidwulff.co.uk

One 18yrs male, red and white, good condition; daily servicing required. £500 collect ono.

Brian Azzopardi

Colin Leitner wrote: wine instead of reinventing the wheel Good point. Colin Leitner wrote: lack of Adobe products I don't think so. There is a good substitute called Gimp. I think it's more because of MS Office which has huge mindshare. There are also substitutes for Office, but to be honest, I've never used them. There is no single reason why people don't use linux. It's a combination of things: lack of interest, inadequate technical knowledge, fear of change. bibamus, edamus, cras moriemur

[eat, drink, for tomorrow we die]

Senkwe Chanda

Brian Azzopardi wrote: The Mono project has only ported the compiler and some other bits Yep but apparently those bits are pretty impressive. I think ADO .NET is either fully ported or getting there. They say they only foresee headaches in coming up with a "Windows Forms" like port of...err, Windows Forms *shrug* Anyway, I'm following this one with interest :-) ASP.NET can never fail as working with it is like fitting bras to supermodels - it's one pleasure after the next - David Wulff