Can anyone help me please, maybe sharing his or her own experiences ?
I understand your point of view, Bear, and I think that you're basically right. GWT - or other server-side web component frameworks, build on GWT or not - is an approach one should follow when has got really good reasons to do so: for example, if his or her team has not enough deep web programming skills to survive a big project, and there's no time (or money, as sometimes happens) to train people in technologies they don't know.
Anyway I think that GWT approach isn't bad by itself, as long as one views it as an efford to use a single language for both server and web client side, and use that language as a meta-language to generate web artifacts (html pages, scripts, css).
Aaaaaand ... we're on the march. Stylin. Get with it tiny ad.
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop