Release cycles and why Microsoft triggers me

So lets address the elephant in the room. Why oh why, Microsoft, why do you do this to us?

.NET 7 is said to be ready for release by November 2022. Yes that's right. .NET 6 was only released November 2021 and we're already looking at a new version by the end of the year.

What is even more shocking is the intended support life-cycles for .NET versions. .NET Core 3.1 end of life is December this year, yet is only just being adopted by businesses in general.

Microsoft have stated multiple times that with the new .NET they are not trying to maintain backwards compatibility with older versions (unlike .NET Framework). This means any new version can and probably will bring about breaking changes.

This is especially concerning considering the very short support life-cycles for each .NET version. In the real world businesses cannot afford to stay cutting edge all the time. It takes time and effort to keep on top of breaking changes and to me, it's not fair on businesses or developers for Microsoft to force such a rapid cycle of changes on us.

Whilst I'm all for innovation, this abandons a philosophy that made .NET Framework so great, changes weren't frequent, support life cycles were long. Critical hot fixes were supplied when needed and backwards compatibility was assured.

Abandoning this philosophy might make the developers of .NET itself have an easier time, allow them to mop up mistakes or ship half-baked half-finished solutions (Blazor). But it costs small to medium enterprise a lot more than they will ever care to know.

It also appears like they are so obsessed with syntactic sugar, they overlook important language improvements to C#, but that could be a whole separate blog post.

I am no Microsoft hater, I endorse a lot of their products, but I can't be the only one angered by their decisions?