Note that this is the announcement for the October release, however the November release is now available although it doesn’t have a blog post.
I can’t believe fonts still get released with mainly basic latin support. Languages that don’t use the latin script have a major disability here.
Well it is a font for programming (done mainly in latin script), by designers who speak and write languages that mainly use latin script, for a userbase that too prioritises latin script. I don’t think it’s ridiculous that basic latin support was the MVP.
I know people that use non-English languages with latin scripts use their language in code (because not every code is for international view). I think that programming is done mainly in latin script because latin script is all that’s available mainly. Besides, even if you do your programming in latin your data may be any script in Unicode.
I believe MS is all in on i18n, but these things take time. It’s not as if there isn’t literally hundreds of other fonts available in the meantime, many of them that cover more than latin scripts.
It’s a work in progress, the font isn’t final. The linked post mentions a roadmap, which after some clicking around can be found here:
Indeed. I wonder if there’s a good reason not to merge wide covering fonts like Unifont with WIP fonts until more unicode blocks are implemented.
Doesn’t MS have a “replacement font” functionality, where missing glyphs are filled by a backup font?
I am totally sold on this font. I use it in IntelliJ, (g)vim/MacVim and iterm2. I used FireMono before for years, but this one is better!
no italics, I can’t consider this font. :)
I’m torn for this specific reason between Cascadia and Fira Code, but in the end, I have found that I’m not actually missing the italics for coding in the few places where I had previously used it. Your mileage may vary, and I’ve seen some very well-thought-out highlighting themes that would definitely suffer in a font without italics.