Me: Points out the obvious fact that a monospace terminal renderer requires nothing but a full-screen quad with a pixel shader that fetches glyphs from a coverage atlas. Microsoft:pic.twitter.com/75Kb5fvebL
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Just stop, and run Linux if you want a non-shit terminal!
The PhD is for also doing emojis?
I expect MS people to ask things like... How do you handle 2+ glyphs per cell, like in: ฉันหวังว่าเคซี่ย์จะประสบความสำเร็จ! إِنْ شَاءَ ٱللَّٰهُ! How does the atlas know under which context each glyph will get hinted and which subpixel XY it will appear at? How to blend ClearType?
I expect MS people to raise objections such as, the grid shader can't put diacritics at new XY coords per-cell, right? You need that to support scripts like Arabic, don't you? I'm told that eventually supporting all scripts is on their roadmap.
For those who don't know, rendering text on the GPU without any glyph image storage (just control points and accel structs) is a *completely solved problem*. Anyone thinking there's still something to figure out is woefully unaware of the state of the art. http://terathon.com/font_rendering_sota_lengyel.pdf …
But they are not even talking about that. They think it would be a doctoral thesis to render them _with_ glyph storage! I wish I were making that up but you can read the GitHub thread yourself and see. The combination of ignorance and condescension was rage-inducing.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.