Ugh… We've had one of those developers. Now we're stuck with a legacy GWT¹ SPA that sucks the life out of any developer who touches it.

1: Google's abandoned webapp toolkit where you get all of the drawbacks of writing Java code with none of the benefits.

GWT ouch. Or as I call it "get with the times!"

> some people go so far as to directly claim that something is good because Google uses it.

Angular everything and everywhere and sprinkle it with Material Design!

Not a fan of Angular, am a fan of most of Material Design.

Yeah... "because google|apple|microsoft|ibm|facebook ..." is generally a bad idea on its' own merit. I do like React though. I like similar JSX tooling around inferno and preact too. It's just something close to what I wanted when first playing around with e4x with flash/flex and mozilla browsers.

Do Google still use their closure library + compiler on all their big properties? https://github.com/google/closure-library/

I'm learning Clojure at the moment, don't think I would have heard of Google Closure otherwise

Closure language and closure compiler are two different things. One is a lispy functional language with its own syntax, the other is a jsdoc typechecker and optimizer/monicker.

A lot of what clojure does, Typescript does it really well with it’s types in jsdocs.

They're related. The ClojureScript compiler uses Google Closure as a backend and runtime library