I wish that system fonts could be told the size of the characters of a web font upfront, before the web font was loaded. The system font's glyphs should smoothly fade/morph into the target webfont once it is loaded.
To solve the problem generally would be difficult or equivalent to the effort/data required to download the web font in the first place, but there may be a quick and dirty solution that covers 99% of text in the wild. The easiest case is monos paced fonts. Is there really an excuse why the system font can't be told via Css what spacing/height to use to match the target webfont?
To be more explicit, it is insane that we find it acceptable for text to reflow/ break over lines at different points once the web font is loaded. There is something that bugs me -- On the one hand we are being considerate and trying to make the reading experience pleasant. On the other hand we are being careless creators of jank. Maybe jank is something that primarily irritates nerds and I am overreacting.
I wish yCombinator or equivalent would fund a company or organization that is dedicated to making a complete end-to-end opensource fpga ecosystem. The proprietary tools are crap.
I would be interested in comparing the performance of Uber's first pass "city-fencing" vs a pre-computed 1D array.
EG:
Subdivide a flat projection of earth into n^2 squares.
Create an array of length n^2.
Set the value of each element in the array to a list of canidate geofences(which have area in that square).
Scale lat and long between 0 and 1. Then you can index directly into it with PrecomputedArray[floor(lat*n+long)]
This is trading space for time, may as well choose space here.
Can you measure the blur that I see when I do not wear glasses, and apply the inverse function to an image, like my computer monitor, so that I can see clearly without glasses? What sacrifices would be made -- dynamic range?
Go only supports static linking. No dynamic linking means no linking issues when deploying the same binary across a billion machines in the Googleplex.
Go is one of the few gc'ed languages that supports static linking[0]. As a result it can solve the same problems as Java / Python / etc but makes distribution significantly easier.
[0] There's a whole bunch (Haskell, OCaml, nim) but none of them have the same popularity and corporate backing that Go has.
You can add instrumentation to binaries using DynamoRIO or pin. This isn't currently supported by afl-fuzz out of the box, although there's nothing that makes it fundamentally difficult.
Challenge - Upload a photo of the print, see it in frame.
Extra credit - Take some photos of your frames in natural room settings. Inside the frame, place a color calibration sheet. Find the transformation of the color calibration sheet (EG - how the room affects color, glare, and shadows), and then apply it to the user-uploaded images. Perhaps this could sell the difference between normal and anti glare.
To solve the problem generally would be difficult or equivalent to the effort/data required to download the web font in the first place, but there may be a quick and dirty solution that covers 99% of text in the wild. The easiest case is monos paced fonts. Is there really an excuse why the system font can't be told via Css what spacing/height to use to match the target webfont?