Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Puts C# and the CLI Under "Community Promise"

Posted by timothy on from the if-it's-a-trap-please-clarify dept.

FishWithAHammer writes "Peter Galli of Microsoft posted a blog entry on Port25 today, regarding the explicit placement of C# and the Common Language Infrastructure (the ECMA standard that underpins .NET) under their Community Promise: 'It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions. You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications. ... Under the Community Promise, Microsoft provides assurance that it will not assert its Necessary Claims against anyone who makes, uses, sells, offers for sale, imports, or distributes any Covered Implementation under any type of development or distribution model, including open-source licensing models such as the LGPL or GPL.'" Adds reader anshulajain: "Understandably, Miguel De Icaza is jumping with joy."

4 of 465 comments (clear)

  1. Re:Seriously, who the fuck cares? by binarylarry · · Score: 0, Troll

    I find it pretty amazing when you mention this to most C# programmers, they'll go on about how different C# is from Java. Even though, we when you're worked with both, it's immediately obvious how similar they are.

    Same with the CLR vs JVM, same thing, different name. I guess it's probably a credit to Microsoft's advertising that lower rung programmers think .NET is some kind of revolutionary technology and not a crippled clone of Java.

    --
    Mod me down, my New Earth Global Warmingist friends!
  2. Promise? by 12357bd · · Score: 0, Troll

    Promises from a convicted mono-polist?

    As others have already said: Thanks, but NO thanks.

    --
    What's in a sig?
  3. Re:Seriously, who the fuck cares? by xoluxo · · Score: 1, Troll

    Those links compare C# 1.0 vs Java in 2000.

    C# 1.0 had a few goodies over Java: events, properties, delegates, p/invoke.

    C# 2.0 introduced generics, iterators and a handful of extra features and lambdas.

    C# 3.0 introduced linq, expression trees.

    C# 4.0 introduces dynamic types, optional and named parameters.

    Java in the meantime introduced the worst possible kind of generics. That is what happens when you layoff the entire language design team and let the language bitrot for a decade.

  4. Re:It's about time by RightSaidFred99 · · Score: 0, Troll

    But...why not just leave it ambiguous? Then they can still go all apeshit ("they really are out to get you") later and have more options to do so.

    Now, I know your answer. Why, because they want to suck more people in to their nefarious plot! What was I saying about paranoia, again...?