Hmm not sure it's really anything as bad as Python2/3. I haven't came across a library that doesn't support netstandard (and 99% of those will do async/await) in a long time now.
There are a lot of libs that haven't been updated for years and therefore don't support netstandard. But you probably don't want to be using them outside of very specific use cases given they are likely to be insecure by now.
There definitely isn't a 'we're holding on to netframework' vibe in dotnet, like there was for python2.
There are a lot of libs that haven't been updated for years and therefore don't support netstandard. But you probably don't want to be using them outside of very specific use cases given they are likely to be insecure by now.
There definitely isn't a 'we're holding on to netframework' vibe in dotnet, like there was for python2.