There has been more churn than usual during+following the .NET Framework -> .NET Core migration. Some of it was necessary due to the migration, some of it is ma

There has been more churn than usual during+following the .NET Framework -> .NET Core migration. Some of it was necessary due to the migration, some of it is making up for lost time after being tied to Windows (and very constrained in their ability to make changes) for so long. I understand your pain but I think most of the recent changes are necessary for the long-term health of the ecosystem, and I would not expect the breakneck pace of the last 5 years to continue forever.