VSCode uses full RGB subpixel antialiasing and has for some time.
However, Cursor is using Greyscale antialiasing.
This causes text to look blurry or fuzzy on sub-4K monitors in Cursor while looking much more sharp in VSCode.
Steps to Reproduce
Open any text in Cursor and VSCode and compare it side by side in Windows.
(Note that MacOS and Unix have different rendering engines so this may look different there, but I’m not sure.)
In the attached image, VSCode is on the left and Cursor is on the right.
You can see that Cursor is using Greyscale antialiasing while VSCode is using RGB subpixel antialiasing. Zoomed in it all looks messy, but at normal screen resolution it results in one looking crisp and the other looking fuzzy.
Expected Behavior
Cursor should use the same rendering technique as VSCode and/or have an option to pick which the user would prefer.
I compared two versions of Cursor and noticed the same issue. In the older version, it uses RGB subpixel antialiasing, while in the newer version it uses greyscale antialiasing. In the newer version, my text appears blurry, and I prefer RGB subpixel antialiasing, but I can’t choose it now.
Version 0.50.7 is on the top and Version 1.4.5 is on the bottom.
Some people said that here were other negative side effects for them with this, but it further proves that the rendering is different and can be affected.
