On Tuesday, October 9, 2012 4:38:47 PM UTC+2, David wrote:

> When servlet engines first came on the scene , developers were writing 
> stringified content directly to the HttpResponse.  


Absolutely, from that point of view (and I remember cgi scripts), template 
engines are a big enhancement to what existed before!

But imagine telling developers from a different field, who have never 
looked into web development before, that there's 

- one approach that is based on sending the complete same 
"<html><head>...</head><body><div>...</div></body>" over and over again, 
after using a template to replace just a small part of it.

- and there's a second approach that just gets the necessary data from the 
server, and then updates the view (making use of the specific client's 
features)

Which one would they choose? I believe it might be a hard time arguing in 
favor of the first approach.
 

> Eliminating them completely has always been a tough sell.
>
>
The only significant technical argument against full-ajax is probably the 
SEO argument. Then again, it's not hard to make it work with Google 
Search<https://developers.google.com/webmasters/ajax-crawling/docs/getting-started>.
 
And other search engines, while maybe not treating it perfectly yet, will 
eventually have to improve their strategy, too. (Note: In Germany, this is 
not much of an issue, as Google Search has a market share of 
>95%<http://www.chip.de/news/Suchmaschinen-Statistik-Google-als-Alleinherrscher_54987735.html>
 here)

 

> Eliminating them completely has always been a tough sell.  Luckily GWT 
> does not require this .  
>
>  
I agree. The decision is separate from GWT/other JS framework. And GWT 
doesn't restrict what you can do in web development.

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/MAdGydemJkcJ.
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/google-web-toolkit?hl=en.

Reply via email to