4 ms·
Are you kidding? You realise the CSS has to be requested right? With a seperate request? And that you could probably optimise your individual pixel rendering
by richo 14y ago
Are you kidding?
You realise the CSS has to be requested right? With a seperate request?
And that you could probably optimise your individual pixel rendering css to some kind of binary format?
Like PNG or JPG?
- lukeholder 14y agoIt is crazy and i wouldn't recommend it, but it does not need to be a separate request - that is false. Also, an image WOULD be separate request.
- richo 14y agoNot really. You can inline base64 encoded images. The main problem being that it's about equally as insane as drawing your images with CSS.
- scott_w 14y agoThe separate request is not why it's a bad idea. The reason it's a bad idea is that it needs to be re-rendered every time the user loads that page - which can become significant overhead on devices where CPU resources are constrained e.g. mobile phones.
- olsn 14y agoi don't think the creator intended this to be something to actually use in a productive way - i more believe that he/she wanted to do something cool with the css3 - i think it's a pretty cool idea even if there is no practical use for it
- richo 14y agoI agree. I think it's awesome. My comment was more in reaction to "bye bye images" in the submission title.