|
|
|
|
|
by LocalPCGuy
4021 days ago
|
|
Reasons I don't care for Closure (currently using it in a production project): 1) Depends on both Java and Python. Ugh
2) It's big, and has to be setup anywhere you are doing builds (i.e. continuous deployment)
3) Hard to setup, understand, compose tasks (none of that is impossible to figure out, just harder than many of the alternatives) The article made a minor mistake about Angular - Google is using Angular in over 1,400 internal and production apps (I know, the article just mentioned production, but the number should signify how all-in on Angular Google really is). Oh, and fun side point - they are using the master branch version of Angular (1.x) - the Angular team needs to run not only all of their Angular tests, but also all of the tests for all of the projects that use Angular to ensure they didn't cause any regressions. Overall, Closure is that library you really want to love, but it just rubs you the wrong way over and over again until you decide it isn't for you. (in my experience) |
|