I really don’t like being overtly cynical to the point of sounding derisive, but, I genuinely stopped reading .NET updates years ago, and one of the reasons I never check on them is because I just know they integrated some bullshit APIs for OpenAI or something else equally unreasonable to bake into an API that’s supposed to exist for decades, that requires an internet connection to an unsustainable service. And, lo and below, they proved me right!
This is why I stopped using C#. I learned my lesson about what Microsoft really thinks about their users back when I swore off C#. I stopped using C# because Microsoft tried to remove hot code reloading from the open source, cross platform CLI tooling so they could lock it behind Visual Studio. The guys who develop C# are great, but at the end of the day, it’s owned by Microsoft, and if you’re using a Microsoft product, they see you as nothing more than livestock to cattle into the next marketing venture, whether you want it or not. Whether you want a Microsoft account or not, whether you want Copilot or not, whether you want Visual Studio or not (I definitely don’t).
EEE works well for their bottom-line, but as most things optimized for profit it’s terrible for the commons. This is all pretty sad, but expected. I’m particularly afraid of long term consequences of WSL.
To end on a more positive note, I love tech and will continue investing my time in projects I believe in, and it’s great there’s a vibrant community that feels like that too!
If you read this far, I encourage you to take the time and remove one piece of MS from your life now :)
F# is nice but it has a ton of sharp edges around interop with C# (no pun intended). And everything is written in C# on .NET. If you’re using an F# library, it’s probably the only one you’re using out of all your dependencies, even if you’re using F#. And that means dealing with everything F# desperately tries to hide from you but still leaves open like a live electrical box, including OOP/inheritance and exception handling, which is much more painful in F# than it ever had any right to be, because you’re forced to use them, even if you don’t want to. So basically F# punishes you for using the OOP-centric platform they deliberately targeted.
(Have to say it was hard to find what was exciting about this release, so much AI fluff, but I guess there are some performance improvements at least.)
I’ve been using .NET (along with Blazor and ASP.NET Core) for quite some time, however I always end up feeling completely “tied” to Microsoft as an enterprise. .NET had all the rights to be a really good ecosystem but it ends up being a completely enterprise technology that only “big companies” end up using because of all the advantages that Azure + CORP provides. I’ll be sad if I’m part of the team that developed it and made it happen, as CLR was a really smart approach and the performance wasn’t bad at all for modern workloads.
First class OpenAI API middleware đź’€
I really don’t like being overtly cynical to the point of sounding derisive, but, I genuinely stopped reading .NET updates years ago, and one of the reasons I never check on them is because I just know they integrated some bullshit APIs for OpenAI or something else equally unreasonable to bake into an API that’s supposed to exist for decades, that requires an internet connection to an unsustainable service. And, lo and below, they proved me right!
This is why I stopped using C#. I learned my lesson about what Microsoft really thinks about their users back when I swore off C#. I stopped using C# because Microsoft tried to remove hot code reloading from the open source, cross platform CLI tooling so they could lock it behind Visual Studio. The guys who develop C# are great, but at the end of the day, it’s owned by Microsoft, and if you’re using a Microsoft product, they see you as nothing more than livestock to cattle into the next marketing venture, whether you want it or not. Whether you want a Microsoft account or not, whether you want Copilot or not, whether you want Visual Studio or not (I definitely don’t).
They didn’t bake it into .Net itself, it’s just an open source library you can install separately: https://www.nuget.org/packages/Microsoft.Extensions.AI/9.0.0-preview.9.24556.5
Ollama for example doesn’t require an internet connection, and if you can afford the hardware you can probably sustain using it.
Do you?
I guess a better reason to not read .Net updated is that there is that much new stuff coming to .Net. The updates to C# are more interesting. :)
Same thing for F#. It sounds interesting and in theory I’d love to learn it, but I won’t willingly step into Microsoft’s shadow.
Unfortunately I think MS’ actions don’t have too many negative repercussions for them. According to the Stack Overflow survey, most devs still use Windows (~50% professionally), Visual Studio and VS Code are the 2 most popular editors, and Teams is the most used chat software.
(Obviously SO numbers are biased but I expect it’s away from MS…)
EEE works well for their bottom-line, but as most things optimized for profit it’s terrible for the commons. This is all pretty sad, but expected. I’m particularly afraid of long term consequences of WSL.
To end on a more positive note, I love tech and will continue investing my time in projects I believe in, and it’s great there’s a vibrant community that feels like that too!
If you read this far, I encourage you to take the time and remove one piece of MS from your life now :)
F# is nice but it has a ton of sharp edges around interop with C# (no pun intended). And everything is written in C# on .NET. If you’re using an F# library, it’s probably the only one you’re using out of all your dependencies, even if you’re using F#. And that means dealing with everything F# desperately tries to hide from you but still leaves open like a live electrical box, including OOP/inheritance and exception handling, which is much more painful in F# than it ever had any right to be, because you’re forced to use them, even if you don’t want to. So basically F# punishes you for using the OOP-centric platform they deliberately targeted.
It’s probably more correct to call OpenAI first class Microsoft middleware.
[Comment removed by author]
won’t that be missing the initial
Item:prefix?(Have to say it was hard to find what was exciting about this release, so much AI fluff, but I guess there are some performance improvements at least.)
The performance stuff is first for a reason. It’s a lot if performance stuff.
I’ve been using .NET (along with Blazor and ASP.NET Core) for quite some time, however I always end up feeling completely “tied” to Microsoft as an enterprise. .NET had all the rights to be a really good ecosystem but it ends up being a completely enterprise technology that only “big companies” end up using because of all the advantages that Azure + CORP provides. I’ll be sad if I’m part of the team that developed it and made it happen, as CLR was a really smart approach and the performance wasn’t bad at all for modern workloads.