10 engineers on Hacker News describe using Google Closure first-hand: 2 endorse it, 2 regret it, 2 are mixed.
“our fork of Google Closure Library (GCL)”
endorse · production · swannodette · 2026-07-06 · source ↗ · wrong label?“Unfortunately, my opinions about Closure are colored by how it was used within my org... We should have taken the best of Closure (the compiler, type checking...)”
mixed · production · jawns · 2023-09-28 · source ↗ · wrong label?“the :advanced flag for the closure compiler has caused us some real headaches in production”
regret · production · bnert · 2022-12-15 · source ↗ · wrong label?“it required that you run every JS reference of a classname through goog.getCssName”
regret · production · nostrademons · 2015-10-15 · source ↗ · wrong label?“We minify production JS using Closure Compiler but sometimes that leaves room for improvement.”
mixed · production · moot · 2013-12-02 · source ↗ · wrong label?“Then I wrote a medium sized application in closure, and it worked, and it's maintainable, and it didn't require a lot of server side code, and it was fast.”
endorse · personal · RyanDScott · 2010-12-13 · source ↗ · wrong label?“We run the user supplied code through an instrumentation pass (using Google Closure Compiler)”
neutral · production · foobarbazetc · 2018-06-07 · source ↗ · wrong label?“Code is minified and compiled, using Closure Compiler's @ngInject and @export annotations as required.”
neutral · production · Nitramp · 2014-11-24 · source ↗ · wrong label?“Gmail as written in 100% Closure Compiler code, Closure Compiler was invented for Gmail.”
neutral · production · cromwellian · 2014-11-21 · source ↗ · wrong label?“I'm by no means an Angular fan (similar to the author I use Closure Tools and React where I can)”
neutral · production · rhofmeyr · 2014-10-07 · source ↗ · wrong label?