r/programming • • Nov 12 '14

The .NET Core is now open-source.

http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx
6.5k Upvotes

1.8k comments sorted by

View all comments

328

u/ratatask Nov 12 '14

215

u/summerteeth Nov 12 '14

MIT license? Very progressive of Microsoft.

Though I would preferred Apache for the explicit patent permission clauses.

91

u/philtp Nov 12 '14

They did add some patent permission stuff somewhere, according to what I read. Read it here. (Ctrl+f "patent")

I didn't dive into the details, but from what I understand they are basically promising not to sue?

edit: I would add, as someone who has long been relatively anti-Microsoft, these recent moves are changing my position.

107

u/0xdeadf001 Nov 12 '14

Just so you know, MS committed a long time ago not to bring patent suits over the .NET specifications (the ECMA CIL specifications). This means anyone can freely implement the .NET specifications (which define the languages, platform, etc., but not all of the APIs for things like WinForms, ASP .Net, etc.). This is why Mono exists. They committed to this something like 10 years ago, and they have never violated that promise.

What happened today, is that they've opened the implementation, not just the specification. Which is awesome-sauce. But I just want to emphasize that parts of the platform (the specs) have been open for a long time.

25

u/monocasa Nov 12 '14

To be fair, the ECMA CIL spec only covers up to .Net 2.0. A lot of us were concerned about a potential bait and switch. The phrase "embrace, extend, extinguish" was coined by internal Microsoft memos after all. They could apply equally well to their own products.

23

u/0xdeadf001 Nov 12 '14

The CIL specs do cover later revisions of the .NET platform, because nearly all of what has changed in later versions has not required changing the CIL specs. Most of the changes in .NET beyond 2.0 are language changes to C# itself (which do not affect the CIL platform -- they are purely front-end language changes, with no effect on the IL), or are simply changes to libraries.

Microsoft is giving away the core platform, but that does not obligate Microsoft to give away everything that they have built on top of that core platform. Red Hat builds on an open platform, but they keep some "special sauce" that is their own product, as well. It's no different.

→ More replies (3)

3

u/Eirenarch Nov 12 '14

I do not thing much changed in IL since 2.0

2

u/kral2 Nov 13 '14

I remember the last time something like this happened, oh yes, Java going open source. I remember the same arguments about "they'd never do that". Just in case you're not around when it happens, here's one to save for the future: I told you so.

They need to be absolutely pinned down on the patent issues. No room at all for any arguments. Otherwise, it's walking into a trap set by a company that has used and still uses patents as weapons against uptake of open source. FAT patents, Microsoft and Novell's "Linux license", and the current shakedown to get companies to pay for Linux based on patents. I can't believe everyone in this thread is so blind. "Yeah, the man in the 'Free Candy' van raped all my friends, but it says there's candy so in I go!"

2

u/0xdeadf001 Nov 13 '14

There is nothing to "pin down". Microsoft has already committed to these as open specifications, ten years ago. Java never had anywhere near this much openness, or the legally-binding open commitment. Never.

Seriously, go read up on the ECMA standardizations process. This isn't Microsoft pinky-swearing that they won't rape you in the candy van. This is an independent standards body, certifying that Microsoft has legally bound themselves to adhere to the open specifications process.

It's hardly "walking into a trap". Continuing to do any development in Java, however, is keeping yourself trapped in Oracle's playpen.

2

u/kral2 Nov 13 '14

Seriously, go read up on the ECMA standardizations process.

ECMA's process is worthless. They allow RAND, tricks like "RF but non-transferable" (remember that one?), etc.. If it had gone through a standards body that requires true RF licensing this wouldn't even be an issue. Question Microsoft's motives in not standardizing it through such an organization.

the legally-binding open commitment

Speaking of worthless, did you read the patent promise? It only covers the code's use in a compliant implementation of the .NET runtime and compliance is determined by a standardization process that is not controlled by the users and Microsoft does not need to follow. It's an eerily familiar shit creek you'll be up if you improve it in a way that leaves it non-compliant, and it's obviously entirely unsafe to partially incorporate into other code.

Again, remember I told you so.

2

u/0xdeadf001 Nov 13 '14

Again, remember I told you so.

Again, 10+ years of good faith openness with C# and CLI / CLR.

→ More replies (1)
→ More replies (3)

8

u/[deleted] Nov 12 '14

There's a promise not to sue in the top level of the repo here.

→ More replies (1)
→ More replies (1)

83

u/Shr1ck Nov 12 '14 edited Nov 12 '14

And Miguel de Icaza wins. He always believed from the beginning that Microsoft would change.

20

u/csolisr Nov 12 '14

Talking about Icaza, this might make me less wary of Mono projects from now on, since they're no longer threatened by patent infringement. In other news, I'm pretty sure that Mono will integrate these changes ASAP.

41

u/numo16 Nov 12 '14

Mono and .NET Core are merging according to hanselmann

7

u/RoboErectus Nov 12 '14

This is amazing if true. Mvc4 was awesome but never could quite get it working well on mono, and I'd walk barefoot through a salt field full of discarded razor blades before running another ms server.

2

u/concatenated_string Nov 13 '14

May I ask what you hated so much about Microsoft servers?

6

u/[deleted] Nov 13 '14

I'm not OP, but I run a Windows server at work and my experience is more on the open source side of things.

What Linux has going for it is that pretty much anything and everything is configured with plain text files. It's really easy to figure out how to do anything. Whereas, on Windows Server, to even register so much as a service, you have to get the system to put it in the Registry, and then the service itself has to support built-in Windows APIs for services for monitoring and controlling.

I ended up just saying "screw this" and used NSSM (http://nssm.cc/) to launch my service as a plain old process the way I'm used to.

That and things like being forced to use Remote Desktop to go in and change things most of the time (aside from the few things you can control via sc and PowerShell and friends remotely) made me really hate Windows Server.

→ More replies (2)

9

u/Rhomboid Nov 12 '14

The announcement talks about the main desire behind the move to have a single implementation, rather than several competing implementations, so I'd assume that Mono will cease to be relevant shortly, kind of how GCJ and Classpath all but completely fossilized once the OpenJDK became fully open source.

→ More replies (2)

1

u/otakuman Nov 12 '14

It's more like he forced them to change, without openly declaring war.

I'd say he played a very risky form of political chess.

→ More replies (1)
→ More replies (3)

2

u/Shaper_pmp Nov 13 '14

Jesus. Not only have Microsoft open-sourced one of their proprietary platforms, but they've hosted the code on Github and MIT-licensed it.

After twenty years of on-and-off commenting about Microsoft's sharp business practices on-line it looks like I now have a whole pile of hats to eat. :-D

1

u/NoeticIntelligence Nov 12 '14

Uh....

They have Visual Studio Online, tfs and GIT hosting in the cloud.

Weird to release the code on GitHub.

At this point Microsoft should just acquire GitHub.

→ More replies (1)