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 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.
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…
Especially when it comes to web. Visual Studio still dies of stroke as soon as someone dares whisper the word "razor" in its vicinity, while Rider has no problem understanding Razor templates and providing full autocompletion.
Not to mention Rider is just straight out snappier. And has integrated terminal without any need for extensions.
If .NET is going to stay relevant in the long run, it needs a better reputation for cross-platform development and much better tooling outside of Visual Studio. Newcomers to the language expect it to work well in VS Code, and they are frequently disappointed.
This decision moves .NET backward in areas it already needs to do better in, and to add insult to injury it does so by deleting already-working code.
You just can't change Microsoft. You can put fancy new skins on things and say you're part of the cool kids, but remember the people who made all of Microsoft s terrible moments aren't the young devs that care. It's management.
The only way I will ever use .net is if an actual open source implementation detached from MS happens. Openjdk it.
Congrats on all the foot-shooting, Microsoft. Just as some people think you've changed, reverse course. Billions well spent.
And it's unlikely that Mono will become a viable alternative, since there's a conflict of interests: Microsoft wouldn't want you running arbitrary .NET applications on Linux, they want you to buy Windows.
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.
Ditch Microsoft. Ditch closed computing.
But you are completely right. Especially with the last sentence.
Now, I don't think I'll rewrite my current projects in Elixir, far from it, but just in case...
This is typical Microsoft, so it's unsurprising. But they have a strange way of 'embracing' open source.
I work at MS, and I love .Net, but I'm really frustrated at this. I have a disability and VS Code is far more accessible for me (b/c extensions), but it's painful getting things done compared to VS.
Wouldn't wait around for it to be reviewed/approved... but I'm willing to be surprised.
Once you accept the nature of the abuser, it's a lot easier to get productive and back to some state of happy.
Is Microsoft raping and pillaging OSS? Kinda maybe in some ways... Are they providing incredibly powerful tools and platforms upon which ordinary assholes like myself can build neat shit? Yes also.
I dont think we should always expect to have our cake and eat it too. Seems like some days we are allowed to, and on others we are reminded that magic is not always free.
This aged very well..
