[bellerocky]

I was the person that initiated using the closure library for a team back in 2010. It took ages to release products using it, someone called it the "write more, do less" library and I have regretted the decision ever since, especially when Google came out with Angular which felt like a total slap in the face. Closure Library had half hearted support, and even teams inside Google hated it, which is why Angular probably came about. It felt like a slap because people that bet on Google supporting Closure couldn't just stop using it and start using Angular.

[DenisM]

I feel for you. Same thing happened earlier to me with Google Web Toolkit.

Frankly, it soured me on the whole third-party framework idea, seeing how it was impossible to predict which one will retain support over the years.

[lennel]

It depends on what your desired outcome is. Angular is not as solid, not as fast, nor is the whole product as able to be statically analyzed.

Longer term maintenance is a pleasure with closure, adding new features a breeze, there are tons of exceptionally well tested components and I cannot stress enough how wonderful deep static analysis and dead code elimination is.

[tomjen3]

I don't really think it is fair to compare Angular and Google closure.

Angular is basically MVVM for the web, which is awesome because MVVM is awesome.

Closure is OOP and "lets move heaven and earth to pretend we are still coding java, but with a weird syntax and lambda functions". It appeals to different needs.