News for hackers. Stuff that matters.
Re:JavaScript Modularity Shaming by finishingmove on Wednesday January 07, 2015 @05:22PM (#8853724)
From what I understand, it should work with any JavaScript you feed it. Though, for badly-written source, it may even produce a faulty output when used with ADVANCED_OPTIMIZATIONS. Yikes! (Example from the docs - "Inconsistent property names": https://developers.google.com/closure/compiler/docs/api-tuto...). So it's more about the Closure Library being "certified" to work with it. Someone with more experience feel free to shed some light on this.
Re:JavaScript Modularity Shaming by markuskobler on Wednesday January 07, 2015 @05:43PM (#8853844)
Its just a more aggressive version of name mangling that Uglify also 'suffers'[1] from. The setting does say advanced with good reason.

[1] https://github.com/jadejs/jade/issues/298