Tell HN: The hidden meaning of Google Closure == Closed Source
While closure is itself open-source, the compiled output it generates with advanced optimizations enabled is obfuscated beyond recognition. A top-level function may get renamed to a single-character like "a", or simply inlined.
If you've tried reading the JS source code for Google Maps, for example, then you know what I mean. The net effect is that the JS code becomes analogous to binary files -- effectively unparsable by humans without effort that is greater than starting from scratch.
I think that the release of Google Closure is ushering with it a new era of web applications whose source code is as good as opaque to human eyes.
I don't have a blog, so I figured I'd just blurt it on here.
If you've tried reading the JS source code for Google Maps, for example, then you know what I mean. The net effect is that the JS code becomes analogous to binary files -- effectively unparsable by humans without effort that is greater than starting from scratch.
I think that the release of Google Closure is ushering with it a new era of web applications whose source code is as good as opaque to human eyes.
I don't have a blog, so I figured I'd just blurt it on here.
Thoughts?