Hacker News Reader

I am sure cross platform is useful to some users but not to me. So to me it's all breaking changes for little benefits.

I am not saying .net core is bad, just that the migration is a lot of work. And you need to disable all sorts of compiler warnings unless you are ready to rewrite pretty much all your code to make it nullable ref type friendly. And some day those warnings will be errors.

View on HN

> And you need to disable all sorts of compiler warnings unless you are ready to rewrite pretty much all your code to make it nullable ref type friendly.

Not really. Just disable nullability checking — you can do it project-wide by removing the Nullable tag from your .csproj, and you can continue ignoring nullability.

> And some day those warnings will be errors.

[citation needed]. A lot of code is written without nullability in mind. That includes the .NET Core BCL, AFAIK.

> That includes the .NET Core BCL, AFAIK.

The BCL was completely annotated with NRTs for the .NET 7 release, minus some #nullable disable spots.

Reply on news.ycombinator.com