If so, it seems as if Windows is undergoing a Waylandization. "Yeah, we went ahead and removed those because they're legacy. Modern rendering pipelines don't work that way anymore." I don't WANT a rendering pipeline! I want a surface, and to make calls to scribble on it! That's it!
Very unlikely. Far too many applications depend on those things. It's more likely that they accidentally changed something subtle that happened to break colorForth.
The Wayland idea looks very similar to a Microsoft brain extract: "trust us, it will be the best when it is ready", "your program doesn't work ? update to latest version", "we have updates: we disabled some things which worked before".
But for decades, Microsoft has been willing to support and work on the ancient tech that got it where it is today. The GNOME/FD.o paradigm is like Mao's continuous revolution. Out with the old and in with the new, forever and always, on an ongoing basis. Microsoft is now changing to this model. I suspect it's for similar pragmatic reasons: it's difficult to recruit young and relatively inexperienced programmers if you're just going to put them to work fixing up code bases from the 90s (written in—brotha, eugh!—C and C++). Since we can't get anybody to maintain that old code, it will become a liability in the future, so we're better off throwing it out and telling our users to cope.
(Especially now that .NET Framework was donated to Wine...)
Do you mean Mono, or did I miss something?
I mixed that up to mean that .NET Framework proper was released as open source, but that's unfortunately not the case.