Re: why we probably won't use GWT for a large UI project

Hi,

I would avoid vaadin. Agreed that vaadin looks good out of the box,
vaadin falls back into the poor old fat-client architecture.
GWT supports a real responsive client-server architecture but vaadin
uses GWT like a display server.

You can test the difference using the sample
http://demo.vaadin.com/Calc

Click a number and it tooks 300ms until the calc will display it.
This latency is a direct consequence of choosing the poor old
architecture.

Stefan Bachert
http://gwtworld.de

On 10 Aug., 09:02, Nathan Wells <nwwe...@gmail.com> wrote:
> I would look into vaadin. We just looked at it recently, and I think
> it's a good alternative to straight GWT, but we can't switch because
> it's a pretty significant change.
>
> On Aug 10, 5:23 am, Shawn Brown <big.coffee.lo...@gmail.com> wrote:
>
> > > I'm looking to get this group's feedback before I present my findings
> > > to the team. What do you think?
>
> > If open source is nice then go for gpl and ExtGWT (GXT).  If you don't
> > pay the commercial fee, then you have to open source your project I
> > believe.
>
> > Shawn

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.