3 ms·

Do you use Chrome (on non iOS platforms) or Android? Both are made in Skia, and I don't just mean they can render Skia apps like Flutter apps, I mean that liter

Do you use Chrome (on non iOS platforms) or Android? Both are made in Skia, and I don't just mean they can render Skia apps like Flutter apps, I mean that literally the system views themselves are all in Skia. Native Android apps that aren't in Flutter are also rendered via Skia.

fxtentacle 3y ago
Yes, I sometimes test on Chrome. And I have also implemented JavaScript workarounds because Chrome still cannot handle a plain <table> with 750 rows where each row has a 120px image thumbnail and some text columns without gobbling up gigabytes of memory and/or freezing on weaker machines. I agree with you that both Chrome and Android work quite well in general. But that doesn't change the fact that some of the design decisions have aged badly: "Chrome is still the king resource hog on macOS" "In previous tests, which included a lot more tab switching, and no WebGL and media consumption, Safari was using 10x less than Chrome" https://www.reddit.com/r/macapps/comments/12n7162/part_3_final_browser_energy_efficiency_benchmarks/ https://www.reddit.com/r/macapps/comments/12n7162/part_3_fin... 9 years ago, I myself also shipped apps that were rendering the GUI exclusively on CPU because it's just so much easier to get things to look 100% identical everywhere. But nowadays, those apps are either pixelated or feel sluggish even on modern Macs because Retina displays have easily 4x-ed the number of pixels that need to be drawn. But single-threaded FLOPS has not 4x-ed since then.