Here's how the difference looks like. I now threw more absolute values at it and it's now much better, but there are still some tiny pixels off that you cannot get to with css, I only hope I can unsee that.
Using `toFixed(2)` in my `font-size` randomize code results in this, which is also even faster. Lessons learned, don't use too many different font sizes (nobody is going to see the difference between 0.54321em and 0.54322em anyways).
I just encountered the weirdest chrome performance issue. I have a page with a lot of absolutely positioned single char divs, and… the page takes 1s longer to render if I have a long `font-family` declaration. Is chrome evaluating the font stack for every text fragment separately? #4-5 are with `font-family: Roboto`. #2-3 with `font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Oxygen, Ubuntu, Cantarell, "Fira Sans", "Droid Sans", "Helvetica Neue", sans-serif`. I mean. What?
Am 31. Oktober gibts in Stuttgart ein cooles Event für Kids: Wearable LEDs basteln mit alten Klamotten!
https://chaos.social/media/mghT2lnsTeTfFs9TRHw Ordered these from redbubble. That's horrible quality, even for digital print, grainy as hell. (Of course, no money refund via their site). A thirty year old inkjet in a wet basement can print better than that. While on fire. Operated by my grandma.