Microsoft apologizes! “We made a mistake” | now recovered Net “hot overload” function, will be in Net 6 SDK

Time:2022-1-7

Earlier last week, Microsoft announced in the upcoming release Net 6 has been angered by the removal of a key hot reload feature Net open source community. Just now, Microsoft has revoked its decision to delete the “hot reload function” and apologized for it:

“First and foremost, we want to apologize. We made a mistake in executing our decision and took longer than expected to respond back to the community.”

Microsoft said that first and foremost, they want to apologize. They made a mistake in implementing the decision and took longer than expected to respond to the community.

Microsoft apologizes!

The so-called “hot reload” is a key function that allows developers to change the source code when the application is running and see the effect immediately.

Microsoft apologizes!

Previously, Microsoft had chosen to limit the “hot reload function” to its own visual studio 2022. In this way, the function is only applicable to windows and the cost is very high. According to the verge report, Julia liuson, President of Microsoft’s development department, decided to delete the function because it was a “business centric initiative”

From the Net SDK repo. After the operation of removing the hot reload function caused a “protest” in the open source community, Microsoft has now withdrawn from the upcoming release The plan to remove this key feature in the. Net 6 version. Due to strong opposition to Microsoft’s deletion of this important feature, Microsoft also officially apologized to the open source community.

Microsoft explained in the blog: “with the release time of. Net 6 and visual studio 2022 getting closer, we chose to focus on the hot reload of vs2022 first. We made a mistake in implementing the plan.” “We inadvertently deleted the source code instead of not calling the code path. We underestimated the number of developers who rely on this feature.”.

At the end of the blog post, Microsoft apologized again and said: “our wish is to create an open and dynamic ecosystem for. Net. Like many companies, we are also learning to balance the needs of the OSS community and being an enterprise sponsor of. Net.”

“Sometimes we can’t do this. When we don’t, all we can do is learn from our mistakes and move forward better. Thank you for all your feedback and contributions over the years. We are committed to developing. Net in the open and look forward to continuing to work closely with the community.”

Just now, Microsoft has “approved the pull request” to re enable this code path, which will be included in Net 6 SDK.

Although Microsoft has withdrawn the plan, it will be Net community, but some foreign media said in their comments that “this incident still leaves some ‘shadows’ in the hearts of many developers in the circle
’”。

Of course, the result is good now. I believe, as Microsoft said in its blog, in the process of continuous exploration and self-renewal, it will continue to work closely with the community in the future to create an open and dynamic ecosystem.