Er ... C# isn't proprietary.
Feel free to grab a copy of the spec and implement it yourself.

[edited by - Martee on April 5, 2002 12:01:00 AM]

pro·pri·e·tar·y

1. Owned by a private individual or corporation under a trademark or patent.

It doesn't matter whether the spec is open or not.
Maybe Sun should create an implementation of c#. Let's
see how long that "standard" lasts then.

[edited by - timm on April 5, 2002 12:28:43 AM]

[edited by - timm on April 5, 2002 12:29:12 AM]

quote: Original post by timm
pro·pri·e·tar·y

1. Owned by a private individual or corporation under a trademark or patent.

And who owns what in this case? Is the language spec owned by Microsoft? Is the C# name a Microsoft trademark?

quote:
It doesn''t matter whether the spec is open or not.

If the spec is open, anyone can use, implement, and suggest changes to it. I fail to see how this makes the language proprietary.

quote:
Maybe Sun should create an implementation of c#. Let''s
see how long that "standard" lasts then.

What?

I think I''ll go download Mono and write some non-proprietary C# code using free tools on Linux.

quote: Original post by timm
No, you really shouldn''t look into c#.
What good is a proprietary programming
language? How stable is a language whose
"standard" is defined by a single corporate
entity?

C# has been standardised by ECMA, and is being fast-tracked through the ISO standardisation process. I know it''s trendy to slate MS, but you should check you facts before jumping on the bandwagon.

quote:
C# == VB++

C# is far more like a hybrid of Java and C++.

C# is Microsofts sad attempt to get read of Java. Since java is a great threat to Microsoft. Think of it. If you could write a java program and have it run on any machine that has a VM on it, which is all OS''s right now, then why would you use any other language. So why is Micorsoft scared of Java? Cause this means developer aren''t writing for Windows, and when you''re not writing for Windows your not helping Micosoft out. Hense C#.

****************************
If religious DONOT read
****************************


Jesus was the best skam artist of all times.

quote: Original post by RickyPiller
If you could write a java program and have it run on any machine that has a VM on it, which is all OS''s right now, then why would you use any other language.

Uh, because Java doesn''t deliver?

quote:
So why is Micorsoft scared of Java? Cause this means developer aren''t writing for Windows, and when you''re not writing for Windows your not helping Micosoft out. Hense C#.

Nah, you got it all wrong. Microsoft realizes tha tthere is an impending shitft towards network-based services, and wants to position itself as the premier supplier of development tools for this future. Sun had a great opportunity with Java, but compromised it by refusing to standardize it and open the spec.

Java is a proprietary language. C# is not.

In bold for the ignorant. Microsoft realized this opportunity and thus developed not just C#, but a now ECMA-standardized intermediate language layer and cross-platform specification, both of which have been publicly and freely released (see the Mono project for corroborating evidence - a now self-hosting .NET implementation for Linux and other unices). Furthermore, Microsoft are themselves developing a .Net implementation for BSD, codenamed "Rotor".

I really think you and all the other clueless Microsoft-bashers should take a look at these articles before spouting off on "Big Bad Redmond''s" purposes behind CLI:
[microsoft.com]ECMA C# and Common Language Infrastructure Standards
[itworld.com]Is Microsoft .Net coming to a platform near you?
[wired.com]Opening Up .Net to Everyone

Bashing Microsoft without reason may make you seem cool to the unsuspecting public or the untrained neophytes, but the experienced developer will show you nothing but scorn.

[ GDNet Start Here | GDNet Search Tool | GDNet FAQ | MS RTFM [MSDN] | SGI STL Docs | Google! | Asking Smart Questions ]
Thanks to Kylotan for the idea!