While there *was* a switch to grayscale antialiasing, it is not the the fact that it is grayscale antialiasing now that is making people complain (something people have been using for decades without any serious issues for many years in former versions of Windows), it is rather like that:
Antialiasing is implemented differently now, and it is tied to hardware rendering (something many many people have been complaining about even in Windows 7), and hardware rendering, obviously, cannot be disabled any longer (in Internet Explorer etc.). The pixel grid is no longer respected (rendering across pixel boundaries).
I remember when Firefox started hardware based rendering lots of people were dissatified because of that blurry type rendering. It was not a question of Cleartype or not, but a question of directwrite or not.
As I said before, many here might regret the loss of Cleartype (of coloured subpixel rendering), but looking at this same thread I saw quite a few screenshots posted where people did not even use Cleartype! So consequently, many did not even use Cleartype in Windows before W8 (I always hated it) - even those who did not use Cleartype in Vista or 7 are now complaining!
Ergo:
The absence of Cleartype rendering now is not the real issue.
It is the loss of pixel grid rendering and the loss of options to tell Internet Explorer etc. to use the rendering I want (like in Windows 7 where I could still use good old grayscale smoothing).
Personally, I never knew a single person who actually preferred Cleartype to standard (grayscale) font smoothing on normal TFT screens.
-egman-