Microsoft removes hot reload from open source .NET, locks it to Visual Studio
1–10 of 62 posts
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#2This is typical Microsoft, so it's unsurprising. But they have a strange way of 'embracing' open source.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#3Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#4Instead, they actually ripped out the code.
Other web frameworks have had this functionality for years. .NET just finally caught up, and then they drop it.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#5This is a terrible decision. The feature already works, and if they’re not happy with it, they could just slap a preview/beta flag on it in the docs like they do for many other things. Instead, they actually ripped out the code. Other web frameworks have had this functionality for years. .NET just finally caught up, and then they drop it.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#6I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple platforms and technologies. I've built my own hooks into the hot reload feature, and I've used it to get a tight feedback loop in many different kinds of applications. It's awesome.
I was so excited to be able to point to that feature and say "yes, .NET has a great developer experience - even outside Visual Studio". I haven't always been able to do that. And now... it's going away as a broadly available feature, so that some bean counter can use it to drive usage of a legacy IDE (I love Visual Studio, but let's not kid ourselves about where the future lies).
Immediate feedback (i.e. a fast inner loop) isn't a niche feature - it's an essential element of any creative activity (see: Bret Victor). They are crippling .NET and it hurts to see it.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#7I'm the author of that issue. I think I can be a little more frank here: this is a horrifically short-sighted decision that has me scared for the future of .NET. I have a tremendous amount of respect for the .NET team, and I'm very certain they're not the ones behind this. I've been incredibly impressed by the hot reload solution that the .NET team has delivered. It's worked remarkably well in preview across multiple…
I too have been using it successfully in preview (having been waiting a long time for it). To drop it so close to the launch of .NET 6 is crazy to me.
It’s difficult to take a charitable view of this. The messaging around “needing to reprioritise” feels very disingenuous to me.
We were making so much progress…
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#8Now, I don't think I'll rewrite my current projects in Elixir, far from it, but just in case...
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#9Ditch Microsoft. Ditch closed computing.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#10Welcome to corporate-owned open-source. You COULD fork .NET and add hot-reload back in. But you won't. And they know it.