5 ms·
Want to pack JS and CSS really well? Convert it to a PNG
- cantino 16y agoThat's a cool hack, if impractical.
- ramine 16y agoWonder if it'd make sense to make a lib/gem out of it.
- quippd 16y agoDefinitely not. "And before anyone else points out how gzip is superior, this is in no way meant as a realistic alternative."
- woodall 16y agoThis post follow along the same lines, however a bit more blackhat[1]. He also did another write up about using images to store xss data a while back. It is great if the image is loaded into javascript, other wise it will not work. http://ha.ckers.org/blog/20070604/passing-malicious-php-through-getimagesize/ http://ha.ckers.org/blog/20070604/passing-malicious-php-thro...
- al_james 16y agoCool hack. Of course, running GZIP on your server renders it all useless.
- noodle 16y agooriginal article: > And before anyone else points out how gzip is superior, this is in no way meant as a realistic alternative.
- sjs 16y agoWhat's the use case then?
- noodle 16y agothere has to be a use case?
- sjs 16y agoOf course not! But if there's no use case then this is getting an awful lot of buzz for no real reason other than Ajaxian running a story on it, considering that it's not that new. http://blog.nihilogic.dk/2008/05/compression-using-canvas-and-png.html http://blog.nihilogic.dk/2008/05/compression-using-canvas-an... It's been on reddit or hacker news before, this year iirc.
- noodle 16y agoas the ajaxian article stated, i believe that people are trying to make use of it to squeeze the most out of the size-limited javascript contests that are out there. but, i've not seen an entry that does yet (haven't looked that hard though).
- bmelton 16y agoI think js10k limits entries to those only readable in UTF-8 which, I believe, a PNG (compressed or uncompressed) does not meet.
- damncabbage 16y agoTech demos or challenges, like what people are submitting for 10K Apart.
- jacquesm 16y agoMalware obfuscation.
- RodgerTheGreat 16y agoAnd so the "pure CSS images" trend has come full circle.
- Raphael_Amiard 16y agoThis means you could do a pure css image and put it in a PNG ... ! Mind bending.
- sethg 16y agoI am surprised that an algorithm designed to compress a graphic image would be at all useful for compressing bytes of text.
- pan69 16y agobytes are bytes.
- whimsy 16y agoYou're being downvoted because, simply put, you're wrong. One gigabyte is as large as any other gigabyte, yes, but the characteristics of that gigabyte may be very different. If they're predictable in some manner, you can tailor a compression algorithm to that gigabyte. You can learn some about this by studying linear algebra.
- RodgerTheGreat 16y agoAnd information theory. The salient concept here is the "entropy" of a chunk of data. The maximum degree to which a given sequence of numbers (or symbols, bits, etc) can be losslessly compressed is called Kolmogorov complexity. Wiki away! :)
- whimsy 16y agoWow, super cool! I don't know much about entropy, etc. This is opening my eyes all over again. Thanks!
- wrs 16y agoFor a lossy algorithm based on human vision characteristics (e.g., JPEG) it would be quite surprising. However, PNG is lossless and is based on DEFLATE, a general-purpose compression algorithm. So actually this makes perfect sense. (See http://en.wikipedia.org/wiki/Portable_Network_Graphics#Compression http://en.wikipedia.org/wiki/Portable_Network_Graphics#Compr...)
- 16y ago
- JangoSteve 16y agoUsing the same process (combining data into a png => sending to browser => reading out specific chunks from the png), could you also have a script that combines all the images in your stylesheet into a CSS sprite, sends it to the browser, and then crops out each image on the client-side? Then you wouldn't have to mess with all the trickery required to layout a CSS sprite and positioning it properly in your stylesheet. Of course the compromise would be the performance hit the first time the browser loads your site and has to crop the images out.
- tlrobinson 16y agoOr just do what we do in Cappuccino, and use Base64 encoded data URIs (or MHTML in most versions of IE): http://cappuccino.org/discuss/2009/11/11/just-one-file-with-cappuccino-0-8/ http://cappuccino.org/discuss/2009/11/11/just-one-file-with-... Base64 bloats the size a little bit, but it's recovered as long as you enable Gzip transfer encoding.
- JangoSteve 16y agoInteresting. What are your experiences with handling the disadvantages of using data URIs? [1] The biggest disadvantage that I see is: Data URIs are not separately cached from their containing documents (e.g. CSS or HTML files) so data is downloaded every time the containing documents are redownloaded. Content must be re-encoded and re-embedded every time a change is made. Based on this, it seems like this would still work well for images specified in your stylesheet, but not so much for images that are specified directly in your HTML, because it would bloat HTML file size, and unless the user's browser caches the HTML file itself, they'll have to re-download the large HTML file over and over again. Also, according to Wikipedia, base64 encoding makes the file size 33% larger than the binary file, and compressing it (as with gzip) only shaves off 2-3% of the base64 file size. Is this accurate? If so, it seems gzip encoding the transfer doesn't really recover the file size bloat you mentioned. [1] http://en.wikipedia.org/wiki/Data_URI_scheme#Disadvantages http://en.wikipedia.org/wiki/Data_URI_scheme#Disadvantages EDIT: Now that I think about it, if you base64 encode all the images in your stylesheet, won't that make your website look like ass for as long as it takes to download that stylesheet? Usually, this isn't a big deal because a text stylesheet gets downloaded pretty quickly, but now it will be larger in file size than the total sum of all the images that were specified in the stylesheet.
- donohoe 16y agoBeen there, it's really cool but impractical in many respects and no real performance gain. It's also a bitch if you update code on a regular basis.
- sr3d 16y agoIt was definitely not convenient during development. When I was testing for IE9, every change in the code needed to be encoded to the PNG image. But having an automate build script really helped speeding up things. YUICompressor caught all the major bugs during the build process so as long as my un-minified/unencoded scripts worked, I was pretty sure that the PNG version would work as well.
- X-Cubed 16y agoIt would be interesting to see how it copes with proxy servers (like the ones Opera use) that downscale images to reduce the traffic on mobile networks. It would be a good idea to checksum the code to make sure that it is what you're expecting to receive.
- jdavid 16y agoThis as 3 purposes, 1. show of some neat trick 2. hide code a. hide code on a 3rd party site b. hide code in an image that actually looks like an image ( steganography ), thus hiding parts of the code within several images. for a really good time, hide some unique data on one machine that acts as a key 3. save per file system space i think gzip uses the same compression algorithm as png files so, to reuse this is silly. the browser supports gzip anyways i saw this as part of a 10kapart competition, and maybe they were trying to make up the difference between the actual size of the bits used and the file system size. i think although this is interesting, but, it defeats the point of the 10k limit; which, was there to show what one could do without server side scripts, and I think a build script .... counts.
- sr3d 16y agoI did write to the 10kapart to ask about using this technique before working on the app. Their answer was: "As long as it works in the required browsers and it's 100% client-side you're welcome to use it in your app." So the build script ... doesn't count. As long as everything works in the browser, it's good. The end justifies the means :)
- kls 16y agoThis is what I love about JavaScript right now. The air of innovation is everywhere. It really is an exciting language to be developing in right now. It reminds me of the early days of Java.