Thursday, March 4, 2021

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

... and in the beginning everything is small and fast but you'll see the same problem (also with pure JS or any other technologies) if you build one huge app...

This is similar to the backend problem... Monolith vs. Microservice --> Monolith UI vs. Micro UI... schrieb am Donnerstag, 4. März 2021 um 11:39:14 UTC+1:
Thanks for the information!

Why don't you just separate the project (Maven, etc) in smaller projects and integrate them just in the HTML files DOM / ScriptInjector?

So in general you could build many Micro UIs (many JS files) in GWT and integrate them in one HTML DOM or put them together through ScriptInjector. schrieb am Donnerstag, 4. März 2021 um 02:45:38 UTC+1:
In the past years, My company build a larget HIS frontend platform based GWT ,  The large means: lot of module,  code by java , output to javascript seems beautify
But, when the application more bigger, the compiler package speed more slower;  debug, publish will wait long time...
Recently, we decied to replace gwt with other pure js frontend(like extjs), in order to slove these problem .

在2021年2月13日星期六 UTC+8 下午7:59:20<Craig Mitchell> 写道:
> Sharing POJO definitions between client and server is the biggest advantage of GWT for me along with static typing in the frontend. Can't live without these two.

Not needing POJOs in a dynamically typed language (JS), could be considered an advantage, due to less code needing to be written.  Although, I personally agree that a static typed language is better, even if it is more code.

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
To view this discussion on the web visit

No comments:

Post a Comment