.NET Hot Reload Support via CLI

Pretty encouraging sign given the drama the last few days. In addition to the community response, it’s pretty clear that a number of dotnet and MSFT team members went to bat hard for this. Really happy to see that they won out.

Re: .NET Hot Reload Support via CLI

#5

Post by dgellow » Sat, Oct 23, 2021, 9:42 PM UTC

Well, at least we cannot say they don’t listen to feedbacks.

Re: .NET Hot Reload Support via CLI

#6

Post by oaiey » Sat, Oct 23, 2021, 9:44 PM UTC

He wrote some "face keeping" Blabla but then the key fact: admitting that they made a mistake and misunderstood the community wish.

A step in the right direction.

Re: .NET Hot Reload Support via CLI

#7

Post by radicalbyte » Sat, Oct 23, 2021, 9:47 PM UTC

This is good, but given the amount of terrible decisions in the last few weeks from Microsoft I've lost all trust in them. This will pass, and they'll sneakily do something else.

It's clear from the reaction of the well known alt.net people that this problem is strategic, and coming from above. Nothing in this move signifies a change in that strategy.

Re: .NET Hot Reload Support via CLI

#8

Post by usui » Sat, Oct 23, 2021, 9:49 PM UTC

A hot-button issue gets corrected now, but then they continue to make subtler moves. Why say you love open-source if you keep the juicy bits of Visual Studio Code closed-source? More like you love open-source... for making money.

Microsoft is a big company with changing microcultures all the time. They alone as a whole should not take credit for their open-source endeavors. In general, big contributor names should be emphasized more, so that we know when they leave Microsoft or the project.

Re: .NET Hot Reload Support via CLI

#9

Post by holografix » Sat, Oct 23, 2021, 9:52 PM UTC

I just wrote a comment on the other post about this.

I wonder how this decision was made _behind the scenes_.

Either some negotiation happened and the Visual Studio team got some concessions (smaller target?) or it was mandated from the top.

Both alternatives do not bode well for the VS team.

Re: .NET Hot Reload Support via CLI

#10

Post by Etheryte » Sat, Oct 23, 2021, 9:55 PM UTC

As a small aside to the general discussion, I don't think I've ever seen an accepted reviews list that long. To me that in and of itself speaks volumes about how the development team feels about the business politics going on here.