On Wednesday, December 10, 2025 at 9:09:13 PM UTC+1 David Nouls wrote:
>From what I remember, Google stopped GWT during the time of the conflict between SUN and Microsoft. They had litigation going on around the Java support in IE. I always was under the impression that Google was trying to protect themselves against SUN for the same reason. Why would they have developed J2Cl then? It doesn't make sense. My recollection is that the people doing frontend work knew JS and CSS and Closure and didn't want to change (and it was probably a bit hard to hire for GWT), so the goal was to translate Java to JS to produce a JS lib, with Closure typing, for use with their existing pipeline. They initially tried to add it to GWT proper (IIRC that's how they did it in Inbox at the time), but it wasn't conclusive. Also, their frontend pipeline for Closure is full of optimizations around updates, where browsers only download a "diff" of what changed since the version they had in cache. GWT is duplicating many of those things that they already had, and probably isn't as good. Also the fact that GWT is kind of a "monolithic" build pipeline. -- You received this message because you are subscribed to the Google Groups "GWT Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/3933ee79-3afc-4a5b-8d58-98c631e5c4ean%40googlegroups.com.
