@LobsterTrader11@de1lux@James_M_South tbf he's specifically talking about just {}, the empty case. Which is mostly (but technically not exactly) the same as saying "is not null", which was introduced later.
@davidfowl@thdxr@davidfowl can you pressure Microsoft to change the C# DevKit licence so that it can be used in non-MS products? A permissive LSP is table stakes.
3rd parties exist I know, but we should be able to use the official one.
@davidfowl Love this. Random unrelated feature request - can we have some sort of trace artifact when using Aspire in tests, so we can pull down a file from CI and view what happened in a local dashboard?
.NET 9 is here, and so is C# 13!
Together with @stuartblang, we will explore the sweet syntax of #CSharp 13 and what's new in #dotnet 9.
on 2024-11-20 Wednesday
at 18:00 UTC
#2codeOrNot2code
https://t.co/Voyez1CWvv
@dustinmoris @nickchapsas Thanks @dustinmoris, I'd be happy to join the stream. I'm not using F# as much these days, so would suspect there are better candidates. I'd also love to see the two of you on stream, I think it would be great to watch.
@dustinmoris @dzoukr I started with PHP, and then went to C# and found that _a lot_ more productive, but that's because WebForms allowed me to build things 5x faster (and then I grew to hate it 😅).
I think for non-progranmers Python is highly productive and approachable, but I get it's subjective.
@DamianEdwards @Tashkant From what I gather it will be baked into the OS, so we won't need dotnet support (or the CoW packages) but need Win11 24H2. File.Copy should be near instant on ReFS then.
Seeking help with the upcoming LINQPad macOS release from someone with x-platform C++ skills that's willing to volunteer a day or two before the end of this year on a small project in exchange for a free LINQPad Enterprise license + good karma :)
New blog post: Using #github Actions/Pages with #blazor to run & visualise continuous #dotnet benchmarks with zero hosting costs https://t.co/dVFFKbp9cq
@dustinmoris @mohdjawadi Now if you are shipping a binary then that's a different discussion, and I could see the 3 year cycle being an interesting discussion. But the for platforms, I go for the STS releases, cause it's really no problem at all (even for hundreds of apps)
@dustinmoris @mohdjawadi Runtime updates and deployments should be happening frequently to avoid security vulnerabilities, but they're not.
If you maintain a platform, you should embrace frequent releases. Trying to minimize this is not healthy.
@dustinmoris The idea that you can just leave an app untouched for months/years is not a healthy one, I'm sure there are enterprises where that's common practice, but the answer isn't "do it less"
@dustinmoris We have over 400 dotnet services, we let teams choose if they prefer LTS or STS, and provide automation for the upgrades. It's often a case of reviewing and merging a PR.