"To find early versions of Arial, the Dinamo team had to work with computer technology archivists to get access to some of the first personal computers and operating systems. In the end they found a tool that allowed them to boot up Windows 2000 on their own laptops"
I hope this "technology archivist" charged them appropriately for this monumental task. /s
The interesting thing is that going by that and by Medea's numbers (https://news.ycombinator.com/item?id=45044803), it seems strange that copying from an operating system that was well after WGL4 came out ended up with a glyph list that is significantly short of even WGL4.
By the time that Windows 2000 came out, Arial Unicode had already been published (with Word 2000).
Agreed. This is the first resource that I've come across that so succinctly encompasses the language. Well worth the read to any dev looking to evaluate the language.
Of course the (good) problem with C# is that it's moving so fast, articles like these can quickly become out of date.
I recently picked up the G915 and share the same frustrations. And it's too bad too because the keyboard itself is the best-feeling, lowest wrong-key-pressed keyboard I've ever used.
I'm desperately looking for the same keyboard without the G keys.
Every tool that I use that doesn't have AI embedded just feels clunky. Any repetitive or predictive task that I have to do should have the option of being automated.
In the reflections link at the bottom they have the following:
> I've been unbelievably fortunate to be continuously employed since college, but I'm not sure how to tell you to repeat that.
So they've had jobs while they've applied elsewhere. Also according to their resume (link at the top) they've had 7 jobs since 2014, or about one job shift every year and some change.
I hope this "technology archivist" charged them appropriately for this monumental task. /s