Which AI do people use for GWT, and how do you use it?

What I've been doing is:

1. Asking ChatGPT when designing, just using it from the browser.
2. Using GitHub Copilot via the IntelliJ plugin when coding.

And I just saw, when the free allocation of copilot responses runs out, you can just go to its chat tab, and tell it to use a different AI:

But maybe there are better AI's or ways to use them?

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/0dfe5d96-f072-4a7b-8336-4dfe401429f3n%40googlegroups.com.

Re: State of GWT?

Very much our experience. We build commercial apps, and having used GWT for years we know it inside out, so we can build things fast. Yes, it's in maintenance mode, but that also means it's very stable and throws us zero curve balls. We've looked at other frameworks, but all seem to end up with way more code for similar sized solutions - and we're not JS experts, so working in a single Java codebase is way way more comfortable for us. We do divert into JSNI at times to wire in some libs (codemirror, gridstack etc). But we create minimal bindings for just the API calls we need.

On Friday, 3 October 2025 at 10:37:49 UTC+1 Frank Hossfeld wrote:

A few years ago, i was thinking about moving to React or vue. So I started some pocs to see how thinks work. At the end npm has loaded some malicious code on my computer. Spooky. That's is one of many reasons to stay with GWT. Next, I am familiar with GWT. I know the pitfalls and drawbacks. We'll use GWT, domino-ui, domino-rest, Nalu & Spring Boot and we are happy with it. So, starting a new project, that would be the tool stack. We build business software and get paid for transforming business needs into code. With that tool stack we can create well maintainable and stable software quite fast. We have an incredible low error rate and at least nearly no downtimes.    
 
 Jens is right, GWT is in maintenance mode. After GWT was handed to the community, all work is done by a few people (like Colin, Jens, Thomas, Ahmad, etc) without getting paid. Not sure, but I think, in case more people starts sponsoring the project (https://opencollective.com/gwt-project) this might change.

Craig Mitchell schrieb am Mittwoch, 1. Oktober 2025 um 06:48:31 UTC+2:

> Now I have to build one webapp prototype and I'm wondering if my GWT-fu can still be of any use. Could someone advise what would be the best way to use GWT in 2025?

If you want create a quick and easy webapp prototype, I recommend using https://github.com/NaluKit/gwt-maven-springboot-archetype to generate a framework based off Spring Boot.

IMHO: GWT's ability to shield you from needing to write JavaScript, is as strong as it has ever been in 2025.

On Tuesday, 30 September 2025 at 9:17:26 pm UTC+10 Jens wrote:

Generally GWT SDK is in maintenance mode which means there is no incentive to add new features to GWT. Most current work is done in the compiler, emulation and distangling code dependencies to eventually use maven/gradle instead of ant.

My main pain point with GWT today is actually CSS. CSS is moving pretty fast and GWT is stuck on an old Closure Stylesheets library. Beside that if you really just want to make a throw away prototype I think I would learn a different JS framework for making such prototypes because you simply have to type less code as in GWT with Java. But of course it also depends on the complexity of the prototype as well.

1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?

Many of them which are considered completed are available on github at https://github.com/orgs/gwtproject/repositories?language=&q=&sort=&type=all

Colin made a google sheet back in the days at https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit?gid=0#gid=0 but it might be outdated. I lost track about the status of not yet completed projects.

 

2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?

Personally I just write JsInterop by hand because most of the time you don't need 100% of the API of a third party JS library. Generated code can also be a bit clunky as seen in elemental2 . Beside the generator you mentioned I don't know any other TS -> JsInterop generator. The one of Google is Closure externs -> JsInterop. 

 

 

3. J2CL seems to remain Google's internal toy, right?

Well you can use it but personally I think you are right, it won't be very popular outside google. 

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/81771c5d-5edd-4400-bac7-feb9574ee62en%40googlegroups.com.

Re: State of GWT?

A few years ago, i was thinking about moving to React or vue. So I started some pocs to see how thinks work. At the end npm has loaded some malicious code on my computer. Spooky. That's is one of many reasons to stay with GWT. Next, I am familiar with GWT. I know the pitfalls and drawbacks. We'll use GWT, domino-ui, domino-rest, Nalu & Spring Boot and we are happy with it. So, starting a new project, that would be the tool stack. We build business software and get paid for transforming business needs into code. With that tool stack we can create well maintainable and stable software quite fast. We have an incredible low error rate and at least nearly no downtimes.    
 
 Jens is right, GWT is in maintenance mode. After GWT was handed to the community, all work is done by a few people (like Colin, Jens, Thomas, Ahmad, etc) without getting paid. Not sure, but I think, in case more people starts sponsoring the project (https://opencollective.com/gwt-project) this might change.

Craig Mitchell schrieb am Mittwoch, 1. Oktober 2025 um 06:48:31 UTC+2:

> Now I have to build one webapp prototype and I'm wondering if my GWT-fu can still be of any use. Could someone advise what would be the best way to use GWT in 2025?

If you want create a quick and easy webapp prototype, I recommend using https://github.com/NaluKit/gwt-maven-springboot-archetype to generate a framework based off Spring Boot.

IMHO: GWT's ability to shield you from needing to write JavaScript, is as strong as it has ever been in 2025.

On Tuesday, 30 September 2025 at 9:17:26 pm UTC+10 Jens wrote:

Generally GWT SDK is in maintenance mode which means there is no incentive to add new features to GWT. Most current work is done in the compiler, emulation and distangling code dependencies to eventually use maven/gradle instead of ant.

My main pain point with GWT today is actually CSS. CSS is moving pretty fast and GWT is stuck on an old Closure Stylesheets library. Beside that if you really just want to make a throw away prototype I think I would learn a different JS framework for making such prototypes because you simply have to type less code as in GWT with Java. But of course it also depends on the complexity of the prototype as well.

1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?

Many of them which are considered completed are available on github at https://github.com/orgs/gwtproject/repositories?language=&q=&sort=&type=all

Colin made a google sheet back in the days at https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit?gid=0#gid=0 but it might be outdated. I lost track about the status of not yet completed projects.

 

2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?

Personally I just write JsInterop by hand because most of the time you don't need 100% of the API of a third party JS library. Generated code can also be a bit clunky as seen in elemental2 . Beside the generator you mentioned I don't know any other TS -> JsInterop generator. The one of Google is Closure externs -> JsInterop. 

 

 

3. J2CL seems to remain Google's internal toy, right?

Well you can use it but personally I think you are right, it won't be very popular outside google. 

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/3ead928c-6761-42a2-9578-b48b4c414e69n%40googlegroups.com.

Re: State of GWT?

> Now I have to build one webapp prototype and I'm wondering if my GWT-fu can still be of any use. Could someone advise what would be the best way to use GWT in 2025?

If you want create a quick and easy webapp prototype, I recommend using https://github.com/NaluKit/gwt-maven-springboot-archetype to generate a framework based off Spring Boot.

IMHO: GWT's ability to shield you from needing to write JavaScript, is as strong as it has ever been in 2025.

On Tuesday, 30 September 2025 at 9:17:26 pm UTC+10 Jens wrote:

Generally GWT SDK is in maintenance mode which means there is no incentive to add new features to GWT. Most current work is done in the compiler, emulation and distangling code dependencies to eventually use maven/gradle instead of ant.

My main pain point with GWT today is actually CSS. CSS is moving pretty fast and GWT is stuck on an old Closure Stylesheets library. Beside that if you really just want to make a throw away prototype I think I would learn a different JS framework for making such prototypes because you simply have to type less code as in GWT with Java. But of course it also depends on the complexity of the prototype as well.

1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?

Many of them which are considered completed are available on github at https://github.com/orgs/gwtproject/repositories?language=&q=&sort=&type=all

Colin made a google sheet back in the days at https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit?gid=0#gid=0 but it might be outdated. I lost track about the status of not yet completed projects.

 

2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?

Personally I just write JsInterop by hand because most of the time you don't need 100% of the API of a third party JS library. Generated code can also be a bit clunky as seen in elemental2 . Beside the generator you mentioned I don't know any other TS -> JsInterop generator. The one of Google is Closure externs -> JsInterop. 

 

 

3. J2CL seems to remain Google's internal toy, right?

Well you can use it but personally I think you are right, it won't be very popular outside google. 

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/ab46d33b-b5e6-413b-97a2-72b71524955en%40googlegroups.com.

Re: State of GWT?

Generally GWT SDK is in maintenance mode which means there is no incentive to add new features to GWT. Most current work is done in the compiler, emulation and distangling code dependencies to eventually use maven/gradle instead of ant.

My main pain point with GWT today is actually CSS. CSS is moving pretty fast and GWT is stuck on an old Closure Stylesheets library. Beside that if you really just want to make a throw away prototype I think I would learn a different JS framework for making such prototypes because you simply have to type less code as in GWT with Java. But of course it also depends on the complexity of the prototype as well.

1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?

Many of them which are considered completed are available on github at https://github.com/orgs/gwtproject/repositories?language=&q=&sort=&type=all

Colin made a google sheet back in the days at https://docs.google.com/spreadsheets/d/1b1D9fEqRh5lZ8cqMJtYoc_25rfTRvsuJkTtS2vjgi3o/edit?gid=0#gid=0 but it might be outdated. I lost track about the status of not yet completed projects.

 

2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?

Personally I just write JsInterop by hand because most of the time you don't need 100% of the API of a third party JS library. Generated code can also be a bit clunky as seen in elemental2 . Beside the generator you mentioned I don't know any other TS -> JsInterop generator. The one of Google is Closure externs -> JsInterop. 

 

 

3. J2CL seems to remain Google's internal toy, right?

Well you can use it but personally I think you are right, it won't be very popular outside google. 

-- J.

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/45c1d045-2b10-4b43-9cc2-2680b3948219n%40googlegroups.com.

Re: Digest for google-web-toolkit@googlegroups.com - 1 update in 1 topic

Hi,

for each developer the reasons to choose framework 'X' are different.

These are the reasons I choose GWT for frontend development against a java backend;

1 - simple integration with Java backend. I can use the GWT-RPC mechanism to have the server receive and respond in java objects. This saves me a java -> string -> js conversion as GWT takes care of this and I can do all coding in java and have compile time validation with a simple maven build. Ofc unit/integration testing can achieve something similar with a json interface, but that already requires more effort than just compiling. Simplicity is always a winner in enterprise application development in my opinion.

2 - reuse of developer skills. Frontend has become available with java knowledge only. No need for javascript knowledge.

3 - adaptation to accessibility requirements. With GWT you have full control of the html you generate. So you can generate purely semantic HTML and fully comply with any accessibility requirements. Most component based frameworks do not allow for this flexibility on a tag/structure level.

4 - I can keep pure OO paradigms in front end development. A bit too much to explain - and mb personal preference - but I've never seen procedural or functional programming outperform a good OO design/implementation. With GWT I can apply these OO principles in the UI too.

5 - You are able to keep layout outside of GWT, styling can become a purely css thing. Which is where it belongs and where it's easiest to maintain. Combined with simple semantic html this makes styling a GWT application very flexible. The only class definitions I set with gwt are functional; i.e. descriptive of what the component is, but never for a specific usage (table, table-row, headered-section for instance and not person-table or similar) which also keeps the css maintainable.

Working with a java backend, I haven't seen a more practical UI solution since I started using GWT back around '07 or so.

The exact underlying technology of GWT is not that relevant to me, but what it enables for java applications in the ui development/maintainability side is unbeatable in my book.

rg,

Leon.

On Mon, Sep 29, 2025 at 10:56 PM <google-web-toolkit@googlegroups.com> wrote:

google-web-toolkit@googlegroups.com

Google Groups

Topic digest
View all topics

• State of GWT? - 1 Update

State of GWT?

Gordan Krešić <gordan.kresic@steatoda.com>: Sep 29 04:16PM +0200 I know the topic is broad (and, hopefully, click-baity), but I'm wondering what would be community's recommendation on how to use GWT in 2025?   For reference, I used GWT since Paleozoic (v1.6?), but left last project using it in 2022. Now I have to build one webapp prototype and I'm wondering if my GWT-fu can still be of any use. Could someone advise what would be the best way to use GWT in 2025?   From my homework on the topic, I can see that GWT project itself is still maintained [1], as well as Elemental2 [2] and some other libs [3][4]. However, as https://www.gwtproject.org/ is severely outdated (I can't remember it was ever up-to-date, to be honest), I still have a lot of open questions:   1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?   2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?   3. J2CL seems to remain Google's internal toy, right?   Thanks for any time you decide to spend reading and (hopefully) answering this.   Cheers,   -gkresic.   [1]: https://github.com/gwtproject/gwt [2]: https://github.com/google/elemental2/ [3]: https://github.com/DominoKit/domino-ui [4]: https://github.com/NaluKit/nalu [5]: https://github.com/ltearno/typescript2java [6]: https://github.com/TDesjardins/gwt-ol

Back to top

You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page. To unsubscribe from this group and stop receiving emails from it send an email to google-web-toolkit+unsubscribe@googlegroups.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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/CABjQu7T%2BZObE7_X%3DjAg0tqeM3L7rtD2i596Gf-8CG5dxzz%3DuUg%40mail.gmail.com.

State of GWT?

I know the topic is broad (and, hopefully, click-baity), but I'm wondering what would be community's recommendation on how to use GWT in 2025?

For reference, I used GWT since Paleozoic (v1.6?), but left last project using it in 2022. Now I have to build one webapp prototype and I'm wondering if my GWT-fu can still be of any use. Could someone advise what would be the best way to use GWT in 2025?

From my homework on the topic, I can see that GWT project itself is still maintained [1], as well as Elemental2 [2] and some other libs [3][4]. However, as https://www.gwtproject.org/ is severely outdated (I can't remember it was ever up-to-date, to be honest), I still have a lot of open questions:

1. I remember GWT was in the process of splitting it into many (J2CL-compatible) submodules, but other than searching Maven Central, I can not find any list of them?

2. Is there any better way of integrating recent JavaScript libraries other than manually writing my own Elemental2 wrappers? I know Elemental2 bindings are auto-generated from Closure, so I'm hoping that there may be some tools that could generate them at least from TypeScript as well. Not that there were not efforts [5]. My prototype would have to work with maps and although I see that gwt-ol [6] is still maintained, I'm wondering what would be my options if I have to integrate with, for example, Windy API?

3. J2CL seems to remain Google's internal toy, right?

Thanks for any time you decide to spend reading and (hopefully) answering this.

Cheers,

-gkresic.

[1]: https://github.com/gwtproject/gwt
[2]: https://github.com/google/elemental2/
[3]: https://github.com/DominoKit/domino-ui
[4]: https://github.com/NaluKit/nalu
[5]: https://github.com/ltearno/typescript2java
[6]: https://github.com/TDesjardins/gwt-ol

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/google-web-toolkit/40bb6561-9955-4b54-b06b-0b2152f3a8fb%40steatoda.com.