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
I'm worried that the baby thinks people can't change.
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
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
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 would never use a complete Unicode atlas because it would never be necessary. You just have your parser note each time it sees a glyph index not in the atlas, then you rasterize it into the atlas at that point and assign a glyph index.
In the case of a terminal it would be required to handle unicode, so you would have to be intelligent about it of course. So I suspect the benchmark should be cat'ing a file with continously random unicode chars and the accepted subset of control characters.
I would disagree. While that's a fine benchmark to _also_ optimize for, that is never actually what people are doing. You don't sacrifice your 99.9% case for a .1% case that never happens in practice. So benchmarks should focus on the common case.
The majority of the planet do not stick to 7-bit ascii. It's far from theoretical to "less" a document with pure unicode.
It has nothing to do with ASCII. I think you're misunderstanding what I'm proposing.
Ok, you're proposing a sort of dynamically updated texture atlas I hope. I just pray it doesn't choke as soon as I try to print korean text.
(and reason I hint to ascii is because you're trying to optimize for that case. I concur, it should. But not at the expense of full unicode support)
No, I'm not. I'm saying that you take each Unicode codepoint you encounter, you look it up in a hash, and if it matches something in the atlas, you output that index. If it doesn't, you rasterize into a new slot in the Atlas.
So take Chinese and Korean book and paste them into the buffer, and scroll up and down without jitter. Now it's just sort of jittery but we can do better.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.