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 <[email protected]> wrote: > [email protected] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/google-web-toolkit/topics> > Google > Groups > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > [image: > Google Groups Logo] > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email/#!overview> > Topic digest > View all topics > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/google-web-toolkit/topics> > > - State of GWT? <#m_1841546856757623174_group_thread_0> - 1 Update > > State of GWT? > <http://groups.google.com/group/google-web-toolkit/t/379d75c494647ca2?utm_source=digest&utm_medium=email> > Gordan Krešić <[email protected]>: 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 <#m_1841546856757623174_digest_top> > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page > <https://groups.google.com/forum/?utm_source=digest&utm_medium=email#!forum/google-web-toolkit/join> > . > To unsubscribe from this group and stop receiving emails from it send an > email to [email protected]. > -- 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/CABjQu7T%2BZObE7_X%3DjAg0tqeM3L7rtD2i596Gf-8CG5dxzz%3DuUg%40mail.gmail.com.
