Live data from Hacker News

Clang with Microsoft CodeGen in VS 2015 Update 1

blogs.msdn.com

1–10 of 39 posts

Re: Clang with Microsoft CodeGen in VS 2015 Update 1

#2
Well consider me surprised. I didn't see that coming.

At first though, when I read through I considered "this is exactly what Stallman didn't want to happen with GCC! Companies using the open-source parts to power their own proprietary tools".

And then I read at the end that they intend to submit most of the things they've done back to LLVM/Clang.

Microsoft is actually starting to act like one of the good guys.

Re: Clang with Microsoft CodeGen in VS 2015 Update 1

#3
post #2

Well consider me surprised. I didn't see that coming. At first though, when I read through I considered "this is exactly what Stallman didn't want to happen with GCC! Companies using the open-source parts to power their own proprietary tools". And then I read at the end that they intend to submit most of the things they've done back to LLVM/Clang. Microsoft is actually starting to act like one of the good guys.

>Microsoft is actually starting to act like one of the good guys.

Morality doesn't need to come into it - they have real incentives to push changes back to master even without restrictive licenses.

Re: Clang with Microsoft CodeGen in VS 2015 Update 1

#6
post #2

Well consider me surprised. I didn't see that coming. At first though, when I read through I considered "this is exactly what Stallman didn't want to happen with GCC! Companies using the open-source parts to power their own proprietary tools". And then I read at the end that they intend to submit most of the things they've done back to LLVM/Clang. Microsoft is actually starting to act like one of the good guys.

>Microsoft is actually starting to act like one of the good guys. Morality doesn't need to come into it - they have real incentives to push changes back to master even without restrictive licenses.

Even for weird little side projects, it's always feels safer to me to get changes upstreamed than keep carrying around "special snowflake" vendored copies that diverge.

Re: Clang with Microsoft CodeGen in VS 2015 Update 1

#7
post #2

Well consider me surprised. I didn't see that coming. At first though, when I read through I considered "this is exactly what Stallman didn't want to happen with GCC! Companies using the open-source parts to power their own proprietary tools". And then I read at the end that they intend to submit most of the things they've done back to LLVM/Clang. Microsoft is actually starting to act like one of the good guys.

>Microsoft is actually starting to act like one of the good guys. Morality doesn't need to come into it - they have real incentives to push changes back to master even without restrictive licenses.

I can't find the link (though I'm sure it was on HN at the time...), but there was a talk by the Sony PS4 compiler people that touched on this a while ago. They ended up open sourcing as much PS4 stuff as they could, not because they wanted to as such, but because it was taking them too much time to do the merge each time they updated their copy.

Re: Clang with Microsoft CodeGen in VS 2015 Update 1

#8
post #2

Well consider me surprised. I didn't see that coming. At first though, when I read through I considered "this is exactly what Stallman didn't want to happen with GCC! Companies using the open-source parts to power their own proprietary tools". And then I read at the end that they intend to submit most of the things they've done back to LLVM/Clang. Microsoft is actually starting to act like one of the good guys.

>Microsoft is actually starting to act like one of the good guys. Morality doesn't need to come into it - they have real incentives to push changes back to master even without restrictive licenses.

You're right, Microsoft has pushed a lot of changes upstream to projects in the past for it's own selfish reasons. That doesn't mean said changes are bad, a lot of times they're fixing problems that they're tired of having to provide support for to end users.
Post reply on HN