Important Notice - Forums is archived

To simplify things and help our users to be more productive, we have archived the current forum and focus our efforts on helping developers on Stack Overflow. You can post new questions on Stack Overflow or join our Discord channel.

Product icon

Vaadin lets you build secure, UX-first PWAs entirely in Java.
Free ebook & tutorial.

why IT MILL ?

Anonymous Anonymous
1 decade ago Mar 04, 2009 3:59pm
Marko Grönroos
1 decade ago Mar 04, 2009 5:00pm


There's no really choosing between GWT and IT Mill Toolkit, as GWT is part of the IT Mill Toolkit. You see, GWT is a client-side technology, essentially a Java-to-JavaScript compiler and libraries that allow you to easily make programs that run in the browser as JavaScript. IT Mill Toolkit, on the other hand, is a server-side Java programming framework, where you program applications that run on a web server. IT Mill Toolkit handles the user interaction in the web browser using GWT transparently with Ajax communications.

Certainly, if you need only a client-side application, you could use just plain GWT, but the most common case is that you need a server backend and in any such case the IT Mill Toolkit solution is probably the easiest.

WingS is a server-side Java framework like IT Mill Toolkit, but it uses plain JavaScript for the client-side, very much like the Release 4 of IT Mill Toolkit did some two years ago. The use of GWT for the client-side programming is the major benefit of IT Mill Toolkit over WinS. I'm not sure if there is any detailed comparison of the two on other technical aspects. I'm not sure how active the WingS project is, if you look at the release rate, with the previous release being 11 months ago.

Dmitri Livotov
1 decade ago Mar 05, 2009 9:00am
Anonymous Anonymous
1 decade ago Mar 05, 2009 10:36am
Thomas Pitrou
1 decade ago Mar 05, 2009 10:37am