Protip: Do not use progressive JPEGs to save disk space or network transmission speed. If you want progressive loading, ok, but otherwise, progressive jpegs require disproportionate amounts of CPU effort to decode vs. the savings. E.g. on mobile you're paying with power.
-
-
Replying to @nothings
This probably isn't much better? ;)https://jmperezperez.com/svg-placeholders/ …
1 reply 1 retweet 3 likes -
We really haven't educated the average developer about what computers are, have we Good lordpic.twitter.com/XHCtSVY7Bi
1 reply 1 retweet 4 likes -
Replying to @antumbral @nothings
Only 1000 bytes of sweet, sweet geometric shapes to dynamically push into the DOM and then rasterize and alpha blend and later replace by the compressed image. POWER IS FREE
1 reply 1 retweet 1 like -
the blur in the sample screenshots is at least like 32x32! somewhere a snapdragon texture unit is screaming
1 reply 1 retweet 0 likes
It’s not so bad in WebRender actually, since WR downscales images before doing large blurs on them :)
0 replies
1 retweet
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.