DOM Scripting comments: To obfuscate or not obfuscate, that is the question http://domscripting.com/blog/display/23 There’s a new obfuscator on the block called ShrinkSafe. en Alex Russell http://domscripting.com/blog/display.php/23#comment82 So as the author of ShrinkSafe, I’d like to note that the point was NEVER to write an obsfucator. We don’t strip out newlines or allow the mangling of public API signatures for that very reason. Any file you download that’s been run through ShrinkSafe should still be readable should you open it up in Veknman and say "Pretty Print". I’m somewhat militantly anti-obsfucator, but at the same time, we need latency reducing tools that can be baked into a build process. Hence ShrinkSafe.

As for the advantages (or lack thereof) of mod_deflate and the like, all I can say is that as someone who doesn’t control the eventual deployment environment, I need to make sure that latency is as low as possible regardless of the relative Ops clue of a given user.

]]> Sat, 15 Oct 2005 20:55:59 GMT Dustin Diaz http://domscripting.com/blog/display.php/23#comment79 Lachlan, I think there is a way you can do it with modZip on apache, so I refrain part of my statement. It just won’t cache with gZip (which is the php way of compression). Another draw back is that it’s calling an http request for it everytime. I tried gZipping my style sheet last month and my stats sky-rocketed for my style sheet (yuck). I just never got around to setting up mod_zip…

]]> Fri, 14 Oct 2005 17:07:48 GMT Lachlan Hunt http://domscripting.com/blog/display.php/23#comment77 Dustin, I didn’t know about the caching problem in IE, but I figure: tough luck. If a user’s broken browser doesn’t cache things properly and makes their browsing slower, especially when using compression that’s actually designed to make things faster f or everybody else, then that’s not my problem.

]]> Fri, 14 Oct 2005 01:17:09 GMT bruce http://domscripting.com/blog/display.php/23#comment76 I’m with Jeremy. The web would be nothing more than hyperlinked physics papers and corporate behemoths if it wasn’t for the first browser manufacturers having the "view source" option, as normal mortals wouldn’t have been able to see what’s under the hood.

In a similar spirit of democracy, Jeremy should really get around to publishing his "marquee tag" unobtrusive JavaScript …

]]> Thu, 13 Oct 2005 13:01:30 GMT Dustin Diaz http://domscripting.com/blog/display.php/23#comment74 Lachlan, one problem about gZipping is that IE won’t cache. So it’s either "quick’er’ downloads all the time" or "one long download - then quick’est’ downloads for the rest"

I prefer caching so I’d go for the crunching. Just be sure to keep a local backup of the original "readable" file.

]]> Thu, 13 Oct 2005 07:19:46 GMT Lachlan Hunt http://domscripting.com/blog/display.php/23#comment73 If your server gzips everything before sending to the client, then the file size benefits gained by stripping unnecessary white space and whatever else obfuscators do, is minimal. For any other reason, the desire to hide the source code is in inverse proportion to the value of that code to anybody else.

]]> Thu, 13 Oct 2005 05:14:36 GMT