5 ms·

And thanks to this article I've learned about the Google Closure compiler: https://developers.google.com/closure/compiler https://developers.google.com/closure/

And thanks to this article I've learned about the Google Closure compiler: https://developers.google.com/closure/compiler https://developers.google.com/closure/compiler

Cthulhu_ 7y ago
Is it still relevant and updated nowadays? IIRC that one's been around for at least a decade already.
- lvh 7y ago
  Absolutely. It took a long time for everyone to catch up on basic features (Closure had modules figured out while the rest of the JS community still had several competing standards), but it’s still tremendously effective. The only downside is the compiler itself runs on the JVM, and most developers ostensibly prefer a single platform. Given how much other software you need to make a development environment work, this seems silly to me.
  - Scarbutt 7y ago
    A real downside and the reason it never took off, is that you have to annotate all your Javascript code to really leverage the Closure compiler. Google also doesn't really advertised the use of Closure, you have to go out of your way to find it in their developer website or google it to find it. It's really just an internal tool. They break backwards compatibility in the Closure Library so much that projects that adopted Closure (like Clojurescript), are stuck with a library from 2017. The project is maintained only to serve Google.
    - nathell 7y ago
      > They break backwards compatibility in the Closure Library so much that projects that adopted Closure (like Clojurescript), are stuck with a library from 2017. The project is maintained only to serve Google. Is that the case? The current version of ClojureScript depends on org.clojure.google-closure-library 0.0-20191016 – I know it's a fork, but I'm not sure to what extent it is being synced with upstream.
      - Scarbutt 7y ago
        Their repo says they are using version "0.0-20170809-b9c14c6b" https://github.com/clojure/clojurescript/blob/master/deps.edn https://github.com/clojure/clojurescript/blob/master/deps.ed... https://github.com/clojure/clojurescript/blob/master/project.clj https://github.com/clojure/clojurescript/blob/master/project...
  - nathell 7y ago
    There is a JavaScript port of the Closure compiler, available from npm: https://www.npmjs.com/package/google-closure-compiler https://www.npmjs.com/package/google-closure-compiler
- jyriand 7y ago
  ClojureScript leans heavily on google closure.
  - Scarbutt 7y ago
    yes, but since we are talking about size, a hello world Clojurescript is going to be at least 80KB or greater.

And thanks to this article I've learned about the Google Closure compiler: https://developers.google.com/closure/compiler https://developers.google.com/closure/compiler

Cthulhu_ 7y ago

Is it still relevant and updated nowadays? IIRC that one's been around for at least a decade already.

lvh 7y ago
Absolutely. It took a long time for everyone to catch up on basic features (Closure had modules figured out while the rest of the JS community still had several competing standards), but it’s still tremendously effective. The only downside is the compiler itself runs on the JVM, and most developers ostensibly prefer a single platform. Given how much other software you need to make a development environment work, this seems silly to me.
- Scarbutt 7y ago
  A real downside and the reason it never took off, is that you have to annotate all your Javascript code to really leverage the Closure compiler. Google also doesn't really advertised the use of Closure, you have to go out of your way to find it in their developer website or google it to find it. It's really just an internal tool. They break backwards compatibility in the Closure Library so much that projects that adopted Closure (like Clojurescript), are stuck with a library from 2017. The project is maintained only to serve Google.
  - nathell 7y ago
    > They break backwards compatibility in the Closure Library so much that projects that adopted Closure (like Clojurescript), are stuck with a library from 2017. The project is maintained only to serve Google. Is that the case? The current version of ClojureScript depends on org.clojure.google-closure-library 0.0-20191016 – I know it's a fork, but I'm not sure to what extent it is being synced with upstream.
    - Scarbutt 7y ago
      Their repo says they are using version "0.0-20170809-b9c14c6b" https://github.com/clojure/clojurescript/blob/master/deps.edn https://github.com/clojure/clojurescript/blob/master/deps.ed... https://github.com/clojure/clojurescript/blob/master/project.clj https://github.com/clojure/clojurescript/blob/master/project...
- nathell 7y ago
  There is a JavaScript port of the Closure compiler, available from npm: https://www.npmjs.com/package/google-closure-compiler https://www.npmjs.com/package/google-closure-compiler
jyriand 7y ago
ClojureScript leans heavily on google closure.
- Scarbutt 7y ago
  yes, but since we are talking about size, a hello world Clojurescript is going to be at least 80KB or greater.