I agree. It is indeed a bit worrying. I am guessing everyone is quiet because Microsoft wants to give a single unified response. And needs some time to prepare and make a decision.
I just hope this will get resolved soon without any issues and we can move on.
Call me naive or uninformed, but I think everyone is overreacting.
I have been using .NET for many years now, preferring VS Code or similar editors for work where I am totally in control of what is going on behind the scenes. I have been extremely satisfied with the direction Microsoft has been taking .NET and also GitHub/VS Code in recent years.
The hot reload feature has been introduced in .NET 6 preview builds - emphasis on "preview" builds. I personally haven't used the feature a lot but have heard it worked great for a lot of developers. And now with .NET 6 GA date quickly approaching, Microsoft is wrapping up the .NET 6 release. This of course means moving any unfinished work to .NET 7, such as full AOT that I was personally looking very forward to. And even MAUI etc...
So after reading their latest blog post on their decision to move the hot reload feature to only Visual Studio for .NET 6 GA, I quickly understood they probably just didn't have time to finish the feature / reach an acceptable level of quality for the dotnet CLI, so they just moved it for a later release - like any other unfinished feature.
Of course this upset a lot of developers that were already using it successfully in their workflows, but let's be honest now, it was always a preview feature. You shouldn't take preview features for granted. I do agree, however, that Microsoft could've handled this better - they could've added like a "preview/experimental feature" warning when using hot reload via the CLI or something and kept the feature there as is - but I'm guessing they wanted to keep their CLI clean of unfinished features. It's not like they said they will never release it to everyone - just that it will be available through VS and VS for Mac for .NET6 GA.
And if Microsoft truly did this for their own "evil" reasons, why was this feature available in the preview builds to begin with?
It's barely been a few days since the blog post, and the backlash is already huge - people are already losing trust in Microsoft and they haven't even given a response yet.
I just hope this will get resolved soon without any issues and we can move on.