Earlier quoted context omitted.
Replace ".NET" with "Windows" maybe? AS a longtime original VB/Winforms developer - MS lost their mind on desktop development and didn't look back. They chased EVERY fad that could be chased. Silverlight, UPF, XAML, WPF, Islands, MAUI. This is one of those things - imagine if they'd focused on building an amazing and cross platform (ultimately) toolkit with just a basic drag and drop designer? Who cares about "stylin…
Not only lost productivity, but getting executive buy in to invest in WPF was difficult after Silverlight. Kinda joking, kinda serious, but all the Microsoft UI changes in the last 10-15 years have definitely helped enterprise IT adopt internal web applications. :)
.NET 6 Released
91–100 of 428 posts
Re: .NET 6 Released
#92I'm glad that Openssl 3 and more support for WASM was added. I doubt that anyone will use WASM though.
Re: .NET 6 Released
#93Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…
Outside of a few very small stumbles, I don't think that Microsoft is a bad steward of open source .NET. Especially if you use Java as the alternative example where there were decades of Sun/Oracle shenanigans around open source Java. Microsoft has done an amazing amount of work writing and rewriting code to make cross platform open source .NET a real thing. All open licensed and developed in the open.
It's fitting you mention all the work Microsoft has done rewriting code. You're talking about .NET itself but I'm talking about the ecosystem, where Microsoft often does take others' projects and release their own version (the Windows package manager comes to mind), training the community to only trust things that come from them. Of course there was the recent famous example of Microsoft deleting public code so they could feature it in Visual Studio, but this tweet is typical of the attitude I've seen from the community: https://twitter.com/GeoffreyHuntley/status/14540569884432179...
Re: .NET 6 Released
#94Is there any reason I should care about .NET today if I'm not already in the ecosystem? I've done C# professionally in the past, and C# is a good language. I wish Microsoft focused on open source and wider industry adoption for C#/.NET sooner so that it could have taken some share from Java. Now .NET is finally open source but Microsoft is a bad steward of the open source ecosystem for .NET, and I certainly wouldn't…
Could you expand a bit on that?
I used .Net 1.1 and 2.0 for awhile, and coming back to it now while deciding the future path for our application.
Re: .NET 6 Released
#95MAUI was the big release I was looking forward to most with .NET 6, appears to be postponed.
Re: .NET 6 Released
#96As a relatively new engineer (~2 years FAANG experience), there seems to be a connotation around .NET. Perhaps this is indicative of the larger Microsoft ecosystem, but it feels like my peers at university and in the industry tend to stay far away from .NET for personal projects, etc. Why is this?
Probably because of licensing costs. Take for example SQL Server. If you want to use it on a server with more than 128GB or RAM you have to get the enterprise version which is licensed per core and the cost is in the thousands per each core pair. Sure, you get a discount, but still the price is steep.
Re: .NET 6 Released
#97Earlier quoted context omitted.
>> Single files apps no longer extract any core runtime assemblies to temporary directories I might be ignorant here but if you're not specifically pointing out what version DLL's you want, aren't you in fact publishing a dynamically linked executable instead of a statically linked one? Doesn't these single-file apps rely on the GAC?
The whole runtime gets included in the binary.
Re: .NET 6 Released
#98MAUI was the big release I was looking forward to most with .NET 6, appears to be postponed.
> .NET MAUI will be released a little later than .NET 6 I wonder when, that could mean 2022
https://devblogs.microsoft.com/dotnet/update-on-dotnet-maui/
Re: .NET 6 Released
#99Been thinking about switching to Rider (already had the personal license for Jetbrains from wanting CLion for Rust) and figured .NET 6 would be a good time to try making the switch. With how blah VS has been for a while hopefully I'll like the Rider experience better (for both c# and f#) Edit: Though I saw something this morning when I tried to load an f# project I made in VS refused to load even though the new ones…
Rider is not perfect, but in many ways miles above Visual Studio.
As Rider doesn't have any Forms editor build-in (AFAIK), I am slowly switching most of my views to fully code, so I don't need to rely on Visual Studio's visual layout editors anymore.
Re: .NET 6 Released
#100Been thinking about switching to Rider (already had the personal license for Jetbrains from wanting CLion for Rust) and figured .NET 6 would be a good time to try making the switch. With how blah VS has been for a while hopefully I'll like the Rider experience better (for both c# and f#) Edit: Though I saw something this morning when I tried to load an f# project I made in VS refused to load even though the new ones…
Rider feels so much faster than VS, and is rock solid - these were my 2 main reasons for switching from VS.