This feels more like an internal turf war inside Microsoft. The general open source strategy with .NET Core and VS Code has been running long enough that I don't think it's just a smoke screen. But there's probably plenty of different interests inside Microsoft that are at least partially in conflict. The Azure side probably doesn't care about selling Visual Studio, but they care about developer mindshare and reputat…
.NET Hot Reload Support via CLI
81–90 of 267 posts
Re: .NET Hot Reload Support via CLI
#82This is reductive, but I am going to repeat the idea that you should not be trusting Microsoft in the first place. Their GitHub acquisition, VSCode, and CodeSpaces are clearly a moat-building towards making GitHub yet another version of Office 365 where you have to pay $$$ for developer tools. GitHub's workflow already bears little resemblance to a "real" Git workflow, and in 7-10 more years I predict that they will…
Re: .NET Hot Reload Support via CLI
#83Earlier quoted context omitted.
> 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. I really dislike this mindset. Sure, it's disappointing that some pieces of VSCode aren't open-sourced, but man, they open-sourced an entire IDE and plugin ecosystem. That's such a fantastic contribution to the open source community, and yet I see comments like yours that…
They didn't make VSCode altruistically, they did it to kill a raft of competing text editors that were on the rise. Atom, Sublime Text, etc etc. I think you call it commoditize your complements.
Re: .NET Hot Reload Support via CLI
#84I 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.
The Verge has an article about this.[0] >The Verge understands that the decision to remove the functionality from .NET 6 was made by Julia Liuson, the head of Microsoft’s developer division. Sources describe the move as a business-led decision, and it’s clear the company thought it would fly under the radar and not generate a backlash. Engineers at Microsoft that have worked on .NET for years with the open source com…
EDIT: grammar
Re: .NET Hot Reload Support via CLI
#85Microsoft are a lost company. They fumbled the cell phone era They half heartedly entered the hardware business with poor results. They have a few golden gooses that could be disrupted at any time (Windows, Office). The biggest asset is dotnet and if they fumble that they will go down hard.
Re: .NET Hot Reload Support via CLI
#86This is reductive, but I am going to repeat the idea that you should not be trusting Microsoft in the first place. Their GitHub acquisition, VSCode, and CodeSpaces are clearly a moat-building towards making GitHub yet another version of Office 365 where you have to pay $$$ for developer tools. GitHub's workflow already bears little resemblance to a "real" Git workflow, and in 7-10 more years I predict that they will…
But I agree with the thesis of your comment.
Re: .NET Hot Reload Support via CLI
#87Earlier quoted context omitted.
The Verge has an article about this.[0] >The Verge understands that the decision to remove the functionality from .NET 6 was made by Julia Liuson, the head of Microsoft’s developer division. Sources describe the move as a business-led decision, and it’s clear the company thought it would fly under the radar and not generate a backlash. Engineers at Microsoft that have worked on .NET for years with the open source com…
While I'm sure the business drove the decision, some developer had to make the pull request, no? What I wonder is whether a "lose your job if you don't do as I wish" gun was stuck to a developer's head, or did they find the right developer with the right permissions to push this change through in spite of resistance? The former option gives me shudders, while the latter saddens me. EDIT: grammar
Re: .NET Hot Reload Support via CLI
#88>> We underestimated the number of developers that are dependent upon this capability in their environments across scenarios, and how the CLI was being used alongside Visual Studio to drive inner loop productivity by many. That's a very odd way to say "modern developers don't use Visual Studio."
Re: .NET Hot Reload Support via CLI
#89Earlier quoted context omitted.
Has anything ever actually replaced VS? I've only ever used VS for hobby/side projects, and even 10 years ago it was leaps and bounds better than what I have to use for my professional day to day work now (code completion, debugger are the two things that I miss basically every day). The tools that I use now have these features, but they're such a joke in comparison. The code completion has no notion of "code", it's…
For many workloads (at least .NET), JetBrains Rider. For C/C++ on Windows, well, you have VS Code and also JetBrains CLion, but IMO CLion is surprisingly rougher than Rider, even though it's older. You can get stuff done though.
Re: .NET Hot Reload Support via CLI
#90Earlier quoted context omitted.
Encouraging? Microsoft demonstrated here that the move wasn't because of quality or that the change was unable to be in the OSS version, they demonstrated that they only act a certain way because of the backlash. If they would have stand their ground, they would have given the image that this change didn't live up to their wanted quality, instead this demonstrated that they are just giving up to peer-pressure because…
What's bad about not wanting to lose developer love?