3 ms·
I suspect what you're seeing is a bit of "I've got a hammer and everything looks like a nail" in relation to the fancy shiny GWT thing that some teams at Google
by cmrdporcupine 5y ago
I suspect what you're seeing is a bit of "I've got a hammer and everything looks like a nail" in relation to the fancy shiny GWT thing that some teams at Google built at the time. IMHO GWT was an awful toolkit and had a slow and terrible development cycle, but there was a lot of hype about it back then as if it was solving the bridge between dynamic front ends and backends written in Java.
I wasn't even at Google at the time but had management types trying to foist it on me at a company I worked at, and it was frankly a failure. I'm not sure if Google Video was done in GWT, but it certainly had the look of a GWT product.
When I came to Google in 2012 there were still some products using it but it was mostly recognized for being clunky and those products have been migrated.
- nostrademons 5y agoPretty sure it was GWT. I joined in 2009 when they were in the midst of the rewrite.
- deleted 5y ago[deleted]
- w0mbat 5y agoIt was not GWT. I worked on it from 2004 (months before launch) to the first couple of years as a live service. It was Java servlets, generating HTML and JavaScript, using some kind of templating system that was in place when I started, taking over from the previous front-end guy. There was no translating Java to Javascript, which is GWT's thing. In fact there was not that much Javascript involved in the early site, it was generated HTML with a smattering of JavaScript. The goal initially was to look like Google search as much as possible and capitalize on the users familiarity with that.
- deleted 5y ago[deleted]