41–50 of 124 posts
Earlier quoted context omitted.
---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!
Out of curiosity, would you have been able to read the actual source if you wanted?
Yeah, I've never tried, but I have a copy of the actual Windows source tree, so I'm guessing the answer is yes.
Should have just used dotPeek instead of ilspy and writing IL code by hand. Recompiling would have certainly been easier. http://www.jetbrains.com/decompiler/
---Author here--- AWESOME TIP, stoked to try it out, thanks!
Awesome read btw!
Earlier quoted context omitted.
i'm glad someone who works at the company like you was able to enlighten us as to microsoft's internal practices oh wait
It's one of the things Nadella has talked about, and plans to address over time (the extreme compartmentalism of and fierce "not made here" attitude a lot of departments/groups within Microsoft have developed over the past few decades.
Earlier quoted context omitted.
---Author here--- I should disclose that I actually work for Microsoft, and still chose the hard way. Fuck the police!
For sure, those who complain about Microsoft not being open source are obviously trying to cover the fact that they are bad at reading assembly language.
Earlier quoted context omitted.
Microsoft already publishes the source code for the .net framework (and I think other projects like asp.net and mvc) at referencesource.microsoft.com
They do, but interestingly that particular assembly is not included. Or at least I couldn't find it there.
http://referencesource.microsoft.com/#System.Core/Microsoft/...
Note: also MSFT employee, don't work on .NET though.
The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
1) You can file bug reports against .NET and they get fixed. (Typically very slowly, but that's enterprise vendors for you...) 2) The tools they used to find & fix the bug are all based on fully-specified, documented, and supported mechanisms: ildasm and ilasm are stock .NET tools, and ilspy is using Mono's IL decompiler/compiler library. 3) You can compile an app against your own builds of any of the standard librar…
Earlier quoted context omitted.
It's one of the things Nadella has talked about, and plans to address over time (the extreme compartmentalism of and fierce "not made here" attitude a lot of departments/groups within Microsoft have developed over the past few decades.
On the other hand, a defense of NIH: http://www.joelonsoftware.com/articles/fog0000000007.html
PS: While the linked article is very relevant here, I'm getting tired of people always linking to Joel's blog -- he's not the definitive software spokesperson; has strong opinions which have been shaped by years at Microsoft - and a lot of his opinions are boxed into those views.
The real news here is that this is considered special. In most other languages, they'd have forked the source, fixed it, recompiled it for their own uses and submitted a pull request or patch. I'm a big .NET fan, but the fact that we have to jump through such hoops to find and fix a bug, and then still have near certainty that we're going to have to reapply the patch for many updates to come, well, that's just a bit…
1) You can file bug reports against .NET and they get fixed. (Typically very slowly, but that's enterprise vendors for you...) 2) The tools they used to find & fix the bug are all based on fully-specified, documented, and supported mechanisms: ildasm and ilasm are stock .NET tools, and ilspy is using Mono's IL decompiler/compiler library. 3) You can compile an app against your own builds of any of the standard librar…
My point is that MS should open source .NET. With a good governance process (super dictatorial no problem! Just be open so we can chip in). It's good for them and for us .NET devs. There's nothing to lose. Like you write, there's a lot of things great about .NET. But being closed source is a disadvantage.