Microsoft backtracks from controversial decision to remove flagship feature from .NET...

nanoguy

Posts: 1,020   +14
Staff member
Why it matters: For the past ten years, Microsoft has undergone a radical transformation from a company obsessed with pushing its closed-source software to one that embraces open-source software and tries to add to it. However, that obsession hasn't been completely removed from the corporate culture, which has led to a lot of drama around the .NET community as of late.

Microsoft has been trying to earn the trust of the open-source community for years, partly because CEO Satya Nadella recognized its growing importance in the grand scheme of things. Back in 2015, Nadella said his company was undergoing cultural and strategic changes in order to help developers and consumers go from “needing Windows to choosing Windows to loving Windows.” Part of that strategy meant embracing open-source technologies and letting Windows as an operating system fade into the background, among other things.

For a company with a long history of trying to destroy open source, this meant a radical transformation of its organizational structure and re-adjusting its goals. One notable example is when Microsoft scrapped its Trident engine and re-built its Edge web browser around the open-source Chromium project, which was started by Google — a rival company that has been eating the web. In 2019, It even joined the Linux Foundation as a high-paying, platinum member and has been striving to be an active contributor to the Linux Kernel.

However, every once in a while, the Redmond company finds itself at odds with the needs and wants of the open-source community. Last week, it made a controversial decision to quietly remove a key part of a feature called “Hot Reload” from the dotnet watch tool in the upcoming release of .NET 6. Mind you, this is a flagship feature that developers depended on to be more productive, so it shouldn’t come as a surprise that it sent shockwaves through both the open-source community as well as internally at Microsoft. It also didn’t help that Microsoft locked and limited a pull request for the removal of that functionality, which also blocked everyone from commenting on the change.

For those who are unfamiliar with Hot Reload, it essentially allows developers to get immediate feedback when they make changes in their projects. The original idea was to bring it to as many .NET developers as possible, but then Microsoft decided to limit that functionality to developers on Windows using Visual Studio 2022, with the remote possibility that it would get added to Visual Studio for Mac sometime in the future. This may make sense from a business perspective but also undermines the ten years of efforts from Microsoft engineers to build trust and contribute to the open-source community.

Since then, Microsoft has reversed its decision and issued a statement admitting it had made a mistake. Scott Hunter, who is the director of program management for .NET, explained that “we made a mistake in executing on our decision and took longer than expected to respond back to the community.” As such, Microsoft approved the pull request from the community to re-enable the Hot Reload functionality in the upcoming release of the .NET 6 SDK, which lands on November 8.

Hunter says the decision wasn’t a business one. Instead, he explained that in an effort to prioritize development resources, Microsoft wanted to enable the functionality in Visual Studio first while it figured out how to bring it to everyone else unbound by the November 8 deadline. Hunter further added that as with many companies, “we are learning to balance the needs of OSS community and being a corporate sponsor for .NET. Sometimes we don’t get it right. When we don’t, the best we can do is learn from our mistakes and be better moving forward.”

That said, this was the culmination of several weeks of drama around Microsoft’s involvement in the .NET Foundation and its questionable influence on its inner workings. One resigning board member raised the question of whether Microsoft is able to resist the temptation to enforce its will on .NET open source and whether or not it can “help foster and promote a healthy community.” The same questions led to the resignation of .NET Foundation executive director Claire Novotny and sent Microsoft scrambling to repair its relationships with the .NET community.

Permalink to story.

 

summermick

Posts: 126   +142
The only id!ots use .Net framework are the US government and its partners. I interviewed for a developer position at LA court, told the recruiter that the CTO is a retard to use Microsh!t for IT infrastructure.
 

bviktor

Posts: 538   +878
The only id!ots use .Net framework are the US government and its partners. I interviewed for a developer position at LA court, told the recruiter that the CTO is a retard to use Microsh!t for IT infrastructure.
Oh wow, you have some serious balls then! Mom should be proud.
 

passwordistaco

Posts: 56   +138
When will Microsoft's commitment to open source reach DirectX?

I'd never heard of .NET anywhere outside of Windows before this article.
 

summermick

Posts: 126   +142
I just got an email says, "Congratulations! You are a finalist for...", don't think the recruiter passed on my comments. It asked me to provide citizenship information, consent to contact my references and do a background check after two weeks radio silence. OMG! I bet two recruiters work on the same case and don't communicate with each other; all my references already got called
 

Ben Myers

Posts: 162   +65
The only id!ots use .Net framework are the US government and its partners. I interviewed for a developer position at LA court, told the recruiter that the CTO is a retard to use Microsh!t for IT infrastructure.
You did not mention the Microsoft-indoctrinated banks and airlines which probably use .NET to front-end their impossible-to-change COBOL spaghetti code.
 
Last edited:

Markoni35

Posts: 1,318   +534
Unity 3D is based on .NET, so a ton of games are written in dotNET. The language on which it relies, C# is an excellent strongly-typed language, with some dynamic features. Definitely much better for serious programming than Python, PHP, JavaScript, Java, etc. The code is easy to read, there are lots of features, execution speed is pretty good, considering it's using JIT.

It used to be slow and memory hungry, with really crappy performance. Just like Java. But both have advanced a lot and modern versions are well optimized, even though still memory hungry, which is really bad on mobile devices.

The worst part is actually how M$ treats the .NET framework. They constantly release new versions that are incompatible with older ones, even in segments that were previously good. Many changes for no good reason. And it's a big, fat framework (though competition is not any better). They had a small one called SilverLight, but they only used it for web, and then scrapped it. Instead of scrapping .NET and extending SilverLight.

But the language is great. In fact, thanks to C# and NET, Unity has the best built-in language among the popular gaming engines.