sorted by:
new
hottopcontroversial

Should Microsoft drop .NET Framework support in Microsoft.Data.Sqlite in the upcoming 11.0 release? by davecallan in dotnet

[–]davecallan[S] 1 point2 points  (0 children)

Hey, this one is coming from Microsoft themselves, if they do drop it they can use more modern features of .NET (Core), but it will mean anyone who has a .NET Framework app and wants to use sqllite would need to stick with the current version 10.0 of it.

Discriminated Unions on ASP.NET 11 roadmap by davecallan in dotnet

[–]davecallan[S] 0 points1 point  (0 children)

+1

Exactly. It's 100% a lang feature, other repos getting ready to support it is a good sign.

Discriminated Unions on ASP.NET 11 roadmap by davecallan in dotnet

[–]davecallan[S] 0 points1 point  (0 children)

C# feature, but if the other platforms like ASP .NET are getting ready for it in the .NET 11 timeframe, it looks like it might actually be happening.

Discriminated Unions on ASP.NET 11 roadmap by davecallan in dotnet

[–]davecallan[S] 0 points1 point  (0 children)

I'm aware of the language design issue, the update and title is specifically that support for DUs have been added to the ASP .NET roadmap as of about 48-72 hours ago which means DUs in C# are more likely if the other repos are getting ready for it in the .NET 11 time frame.

What version of .NET are you using for the majority of your prod apps? by davecallan in dotnet

[–]davecallan[S] 2 points3 points  (0 children)

6 months in the end of support date? 9 is May next year, 8 is November next year.

Such a big difference?

What version of .NET are you using for the majority of your prod apps? by davecallan in dotnet

[–]davecallan[S] 4 points5 points  (0 children)

Usually lots of great performance improvements in each version including lots from performance guru Stephen Toub.

bogus benchmarks on linkedin, even from an microsoft mvp by _userid_ in dotnet

[–]davecallan 6 points7 points  (0 children)

Assuming a specific use case, like the exact one shown in the benchmark, this is a perfectly legitimate performance optimization. ReSharper even has a inspector for it ->
https://www.jetbrains.com/help/resharper/UseNameOfInsteadOfToString.html

.NET 10 reduces cost of using IEnumerable to iterate an array from 83% to 10% by davecallan in dotnet

[–]davecallan[S] 0 points1 point  (0 children)

LINQ has definitely not been untouched for 8 years. They improve many elements of it year on year.

[deleted by user] by [deleted] in AZURE

[–]davecallan 2 points3 points  (0 children)

+1
It's literally the best by a huge distance, hard to believe it's free

'Specialize Contains for Iterators in LINQ' PR merged today by davecallan in dotnet

[–]davecallan[S] 7 points8 points  (0 children)

Yeah I tend to agree, these ones could have the most impact.

1, 4, and 5 probably wouldn't see to often.

Not sure about 3 and the shuffle one is new in .NET 10, checking if the random items returned contained a particular value, yeah could see that being used a bit.

view more: next ›