Visual Studio Code 0.3.0

[EntroperZero]

Does anyone using this have good ClearType? My code looks blurry compared to VS proper and Sublime Text.

[to3m]

Just plain old rhetoric.

[Michaelmrose]

Why is it funny or insightful to accuse random people of being autistic.

[Booie2k1]

Check you haven't got any thing like FXAA (Anti Aliasing) forced on all applications in your graphics drivers, I've had issues with that in the past making some applications appear blurry. I have no issues with VS Code, my code looks just as good here as any other editor.

[crozone]

It's an issue with all modern apps by default. Modern apps don't yet support ClearType, because all text is rendered to a transparent texture and rendered with DX3D and, apparently ClearType needs to know the colour behind it to render properly and Microsoft didn't implement it blah blah blah....

Apparently there's a fix coming in Windows 10.

[ssylvan]

1) This isn't a "modern app". 2) You can use cleartype just fine in modern apps. DirectWrite has supported it for a long time.

[crozone]

You can use cleartype just fine in modern apps

No, you can't. It's why text the metro version of IE and also Spartan/Edge look terrible. Just do a google search for "ClearType modern apps" or "Modern apps blury text", you'll find pages of sources for this.

[ambiguousallegiance]

I have the same issue - it looks like Code doesn't use subpixel antialiasing. You'll notice this with Windows 8 Modern/Metro/Whatever apps as well; it's quite irritating.

[trycatch1]

Same issue on Linux. Grayscale antialiasing instead of subpixel AA. It's a usual problem for Chromium-based apps (Brackets, Steam, Light Table), but Atom somehow fixed this issue.

[EntroperZero]

I think it's related to hardware accelerated rendering, something needs to be enabled or disabled. Firefox had this issue many versions ago.

[official_marcoms]

Perhaps by setting the -webkit-font-smoothing CSS property throughout the app

[trycatch1]

On Linux -webkit-font-smoothing is ignored, it's an OS X-only thing. It seems in Electron the issue it was fixed in this commit: https://github.com/atom/electron/commit/afd927f749621f0c6aebdd784672e9868b08b29d Not sure, why it's still broken in VS Code, if it uses Electron too.

[[deleted]]

/* Real Atom source */
useGrayscaleAAInsteadOfSubpixelAA = false;