2 ms·
Sometimes I feel like the Visual Studio team and the C# team don't talk to each other very much. The C# team says "this is the new best practice" while VS stil
by Pxtl 5y ago
Sometimes I feel like the Visual Studio team and the C# team don't talk to each other very much.
The C# team says "this is the new best practice" while VS still drives you to The Old Way all the time.
- Jorge1o1 5y agoYour gut feeling is very correct. https://news.ycombinator.com/item?id=28972431 https://news.ycombinator.com/item?id=28972431 There was a whole fiasco where the dotnet/C# team were forced to remove features from dotnet in order to sell more copies of Visual Studio. Later, Microsoft lied through their teeth and said it was some kind of sprint-planning scoping error, even though the development work was already done.
- MikusR 5y agoWorst part is that the person that made the decision to remove that feature was promoted. And now indirectly controls GitHub.
- PraetorianGourd 5y agoYou have absolutely no idea what you are talking about. Full disclosure: I know what I am talking about
- pjmlp 5y agoIt is quite easy, the ASP.NET folks on the C# team don't care about the remaining use cases, and they are the ones behind the initial .NET Core reboot. Except, everyone else cares about everything else .NET Framework has been used for the last 20 years. This was quite telling on the .NET 6 release with its minimal APIs to compete against Python and JavaScript "hello world" apps. As soon as one scales beyond that, it is back to the old MVC model.