Not sure what are you complaining about.
If you are single developer or small enough entity who can not afford, you have Visual Studio Community for FREE.
However, if you are making good money developing software then you spend some of it in tooling. Why should your company make the profit but not MS who invests heavily in their platforms, tooling and entire eco system so you can build and run your applications and services (which makes you money in the first place).
I have not seen any more generous company than MS.
Have you?
Microsoft removes hot reload from open source .NET, locks it to Visual Studio
51–60 of 62 posts
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#52They are reverting it back https://github.com/dotnet/sdk/pull/22262
Little more than a troll - a third party clicked the revert button, basically.
Wouldn't wait around for it to be reviewed/approved... but I'm willing to be surprised.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#53Revenge of the donkey
But I wanted the laser cannon!
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#54.NET is one of those languages you want to give a chance, and every time you do, it does something incredibly short sighted and harmful to itself. 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 ac…
I ran across this recently when I wanted to give C# a chance again with a build of the VSCode code base (which everyone should use, also known as Vscodium). Well, guess what: The debugger only runs on the proprietary version of VSCode. The one with the telemetry and nagware.
Congrats on all the foot-shooting, Microsoft. Just as some people think you've changed, reverse course. Billions well spent.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#55"your language is not backed by a big corp, therefore it is useless"
This aged very well..
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#56At some point you have to start asking yourself, why do I tolerate this stuff when there are better alternatives elsewhere? Ditch Microsoft. Ditch closed computing.
I haven't found a more pleasant language and ecosystem to use than C#. Where am I going to go, Java with its verbosity, so my projects double in LOCs? Rust, with its cliff of a learning curve and alien syntax?
If you want Java without the verbosity, try Kotlin: https://kotlinlang.org/
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#57.NET is one of those languages you want to give a chance, and every time you do, it does something incredibly short sighted and harmful to itself. 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 ac…
There's already Mono.
Mono developers have been part of Microsoft for some time already.
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.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#58I'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…
Visual studio is anything but legacy and I haven't found anything better. Where does the future lie?
ever tried razor auto indent? the nuget pm ux? ...
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#59They are reverting it back https://github.com/dotnet/sdk/pull/22262
They are not. Even if they agree with the community. It is too late for release timeline of .NET 6.
Re: Microsoft removes hot reload from open source .NET, locks it to Visual Studio
#60Welcome to corporate-owned open-source. You COULD fork .NET and add hot-reload back in. But you won't. And they know it.
Well, try to squeeze something into Linux without Linus approval. Every project has a ultimate authority somehow.
But you are completely right. Especially with the last sentence.