The idea is to separate UI code from business logic - it has nothing to do with what language you are programming in.
GWT is simply a mechanism to make this separation clean and simple...and let you program in a mature, type-safe, structured manner. - Bob On Jan 2, 3:41 am, geronimo <[email protected]> wrote: > Hi All, > I like the idea of cross-compiling Java into different versions of > JavaScript (one for each web browser\locale). However, aren't we > repeating the same mistakes- embedding UI logic in Java compilation > units. The very reason why JSP came in the market was to separate UI > code from Java code. Developing servlets with embedded HTML was > getting too difficult to maintain. Here's a brief look at how the > technologies have evolved over a period of time: > > Web App Development Landscape > 1997 Servlets - UI code goes in Java compilation units. Java on Server > side is cool! > 1999 JSP- Servlets are difficult to maintain. UI and pure Java code > should be separated. Let Servlets do the heavy lifting and JSPs to > manage the view. > 2006 GWT not again! we're again embedding UI widgets in Java. > > Thoughts? > > Thanks > KJ
-- You received this message because you are subscribed to the Google Groups "GWT-Ext Developer Forum" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/gwt-ext?hl=en.
