Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why? #1

Open
nelsonic opened this issue Sep 19, 2016 · 1 comment
Open

Why? #1

nelsonic opened this issue Sep 19, 2016 · 1 comment

Comments

@nelsonic
Copy link
Member

nelsonic commented Sep 19, 2016

Before we dive into learning about Closure Compiler, we need ask ourselves the question: Why?

  • Why is this useful?
  • What "problem" is this solving?
  • Did the users ask us to write the code using ES6 features, or is this a developer "requirement"...?
  • Is there a use-case for "compiling" JS code regardless of if we are using ES2015/17 ?
@nelsonic
Copy link
Member Author

nelsonic commented Sep 23, 2016

I just installed Google Closure Compiler JS https://github.com/google/closure-compiler-js from NPM:

npm install google-closure-compiler-js --save-dev

And the total footprint is:
learn-google-closure-compiler-11mb

By contrast babel installs 200 Megabytes on your Machine for each project you have it as devDependency...!!
adding-babel-dependencies

Babel takes up _20x_ more space on disk and has _40x_ the file count ... Why...?!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant