That's why they created Dart Yahoo Mail: Search, Organize, Conquer On Wed, Dec 10, 2025 at 8:08 PM, David Nouls<[email protected]> 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.On Dec 10, 2025 at 20:39 >+0100, 'Tim Macpherson' via GWT Users <[email protected]>, >wrote:
, I gather the Google move re gwt was related to angular and maybe react in some way ? Incompatible probably wrong term.I know D3 is incompatible with react, it has optimal rendering and shadow dom would only confuse things. That's a different issue. Yahoo Mail: Search, Organize, Conquer On Wed, Dec 10, 2025 at 7:28 PM, Colin Alworth<[email protected]> wrote:I'd need you to define "incompatible" for this discussion to make sense - the GWT library I described above is used by a (much larger) React app, and I know of several other apps with react+gwt integration (including GWT/Java tooling which lets you build react components in Java). There certainly can be paradigm problems in taking a GWT app and shoving React code into it or vice versa, but the same can be said for taking a plain JS app and adding React, etc - and no one ever says that React is incompatible with JS (though it certainly suggests a particular style of JS). On Wednesday, December 10, 2025 at 1:24:39 PM UTC-6 [email protected] wrote: Another factor was emegence of angular then react, which are incompatible with GWT but considered essential by Google at that time ? Yahoo Mail: Search, Organize, Conquer On Wed, Dec 10, 2025 at 2:59 AM, Colin Alworth<[email protected]> wrote: It is probably worth noting that while Google did drop GWT the compiler and runtime, they continue to ship GWT's JRE emulation in Google Sheets and Gmail (via J2CL and Closure Compiler) in decently large JS files, with a lot of other code that plausibly looks like it shares (1000+ classes each). Java's distinctive Object.toString() behavior makes it pretty easy to find in compiled JS. As Google has described in the past, this lets them write the core runtime for an app in a single language, Java, and translate to build the UI in the most appropriate language for the platform they are deploying to. I'm not aware of many GWT apps that are being used like that, but there are some. For one of them, we built and open sourced https://github.com/Vertispan/jsinterop-ts-defs/ to do the opposite of what you're discussing with d3.js - take Java types with some JsInterop annotations, and generate .d.ts files from them. This way, JS/TS developers can import those types and get rich type information about the Java we compiled to JS. There are a few custom annotations that we've found helpful to add on, but for the most part this tool works with any GWT app using JsInterop to expose some classes/functions as a library. I don't think that is what Google is doing - mostly because they've historically resisted efforts to generate externs from JsInterop, preferring to read Closure-annotated JS and generate Java from it. It has worked well for us though, as there aren't a lot of JS/TS projects outside of Google that are suitable to being passed through Closure on their way to production.On Tuesday, December 9, 2025 at 5:46:54 PM UTC-6 [email protected] wrote: Re: Why did Google drop GWT for it to be superceded by this? My 2 cents worth of guessing is that because GWT protects developers from learning all about JS, developers might not get the most out of JS. Eg: A Java developer sees no issue using integers, but JS doesn't support them, so GWT adds complexity in JS to simulate them. Companies that want the bleeding edge performance might not like this. But, as I said, I'm only guessing here, I've never worked at Google. On Wednesday, 10 December 2025 at 5:07:55 am UTC+11 Tim Macpherson wrote: As a GWT user also using TS when necessary: refactoring: WWD in eclipse for TS, vs VScode, no noticeable difference ? essentially nothing useful in either ? Typing - all must be done manually, syntax is back to front: name then type. Why did Google drop GWT for it to be superceded by this? About the same time they were trying to launch Dart but that went nowhere afaik Yahoo Mail: Search, Organize, Conquer On Mon, Dec 8, 2025 at 11:47 PM, Craig Mitchell<[email protected]> wrote: I'm not sure I understand the question. I've used TS in one project, and GWT in another. Never in the same project. As far as static typing goes, Java (GWT) wins hands down, as it is a native to the language. On Sunday, 7 December 2025 at 6:13:13 am UTC+11 Tim Macpherson wrote: I'm using GWT and TS together, both involve static typing and ide support around that. Basic question is: does anyone else do this (I assume yes) and how do they compare? Yahoo Mail: Search, Organize, Conquer On Sat, Dec 6, 2025 at 9:43 AM, 'RobW' via GWT Users<[email protected]> wrote: Question possibly of interest is how GWT stands against Typescript which seems to be now established as a front end standard. I'm really not sure why Typescript is relevant - if I were coding front-end in JS or TS, then yes I'd think about which syntax and features (type checking etc) were better. But in GWT I'm coding in Java. I don't really care what the compiles down to as long as it works. OK, when debugging I do see the JS output, but I'm never mod'ing that directly. On occasion, to use a lib, I'll quickly craft some JSNI bindings for the methods I need. But that's as close as I go to the JS layer. -- 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/73084908-7b51-456a-a241-3ce263ec7a72n%40googlegroups.com. -- 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/1bd9b354-b1c1-48cb-80a5-85cc7637bcaan%40googlegroups.com. -- 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/f4b210fa-cc06-4778-b5e9-5872e3def908n%40googlegroups.com. -- 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 visithttps://groups.google.com/d/msgid/google-web-toolkit/1bbf7e16-900d-4230-8c09-e0645ab83053n%40googlegroups.com. -- 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/1326152705.39084.1765395560387%40mail.yahoo.com. -- 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/81836c84-ae67-44fa-b7a0-c01ac55324b3%40Spark. -- 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/1497397481.4344802.1765397685629%40mail.yahoo.com.
