91–100 of 267 posts
Nothing about their strategy since has made me regret that decision.
Kind of sad to see them flailing about and screwing up, burning goodwill from VS Code and the like.
DevDiv still doesn’t get it, dinosaurs.
I'm so glad I'm not at Microsoft anymore. Her decisions might be great for Microsoft's profit margins, but my god does she hate people getting "stuff for free"
Earlier quoted context omitted.
That person who messed up just left the foundation btw.
Who's that?
Search Algolia for lots of posts about the recent .NET Foundation kerfuffles.
Earlier quoted context omitted.
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.
Rider is a non-starter - doesn't even have a community edition.
Earlier quoted context omitted.
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.
Rider is a non-starter - doesn't even have a community edition.
Maybe I'm naive, but I fully buy the explanation of "we decided to not have it in the OSS version due to constrained resources" (if I'm parsing the discussion correctly). That was evidently not the smartest move, but attributing it to malice is taking it quite a step further. Change my view.
It's not malice. Your non-technical boss who says "well, if we have 3 other developers developing that API with you, it should get it done in one fourth of the time, right?" is not malicious either. But this kind of a boss doesn't "get" it, and neither does Microsoft. They don't seriously understand the mindset behind an open source project, and I don't expect them to in the future either. So I avoid all Microsoft te…
.NET Framework is another story, and was (and still is) tightly coupled to Windows. It's the entire reason .NET Core was started as a separate open source effort. Honestly, we're lucky .NET Core was even allowed to live as long as it has. Now, it's philanthropic culture is directly butting heads with the profit-oriented culture of the Visual Studio team.
This kind of stains .NET as a whole moving forward. I now qualify .net and C# as a non-starter. Just like I would Oracle for my database needs. Is it fast, great, nice to use? Maybe -- but I won't ever use it because it's riddled with licenses and other bullshit I really don't care about. I'll continue to use truly open source and free tools like Postgres and Elixir.
Earlier quoted context omitted.
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.
Rider is a non-starter - doesn't even have a community edition.
A hot-button issue gets corrected now, but then they continue to make subtler moves. 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. Microsoft is a big company with changing microcultures all the time. They alone as a whole should not take credit for their open-source endeavors. In general, big contributor names should be…
> 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…
This kind of stains .NET as a whole moving forward. I now qualify .net and C# as a non-starter. Just like I would Oracle for my database needs. Is it fast, great, nice to use? Maybe -- but I won't ever use it because it's riddled with licenses and other bullshit I really don't care about. I'll continue to use truly open source and free tools like Postgres and Elixir.
Don't dismiss .NET itself so easily. As you can see from this incident, there are elements even within Microsoft that don't inherently value the open source nature of the .NET team! .NET Core/.NET 5+ are already open source and highly philanthropic in nature. That doesn't change just because a completely different team--the Visual Studio team--is profit-oriented.