Who's still on .NET Framework?

[louthy]

It's now getting to the point where sticking to .NET Standard 2.0 is holding back this library. I realise this poll isn't likely to get seen by many people, so it might not be representative, but could you let me know whether you need .NET Framework support from this library.

[BrunoJuchli]

We're planning to replace all of our .net Framework with .net "core", but unfortunately it'll take about another year until we're finished with that :-/

[MikeCook9994]

My team has a collection of microservices that are still on .NET Framework 472. I actively encourage everyone to drop support for it because it's ammunition that I can use to convince leadership to let us migrate finally.

[louthy]

Thanks for the votes and feedback. The decision has been made to move to .NET8.0 for the upcoming 5.0.0 release -- primarily to leverage:

• The static-interface-members features for Higher Kinds
• Collection expressions (Seq<int> xs = [1,2,3])
• Lambda improvements
• Performance improvements

The enabling of trait functionality with the static-interface members is the big one and has led to a massive refactor -- but it makes the library 1000x more powerful and 1000x easier to maintain. That's something I can't ignore.