From http://www.gwtproject.org/makinggwtbetter.html
We want great results, where "great" is defined by how much it benefits end users. Sometimes there are conflicts between what is easy for us developers and what benefits end users the most. When the two are in conflict, end user experience almost always wins.
We definitely do not view development in GWT as a form of compromise. We firmly believe that GWT should generate better JavaScript code than you would write by hand, and will generally choose to avoid making concessions to convenience if they hurt the performance of the resulting AJAX code.
Does that help?
On Thursday, February 13, 2014 1:00:24 PM UTC+1, Edu Melo wrote:
-- no-compromise AJAX
We definitely do not view development in GWT as a form of compromise. We firmly believe that GWT should generate better JavaScript code than you would write by hand, and will generally choose to avoid making concessions to convenience if they hurt the performance of the resulting AJAX code.
Does that help?
On Thursday, February 13, 2014 1:00:24 PM UTC+1, Edu Melo wrote:
Good morning,I've been using GWT with a superficial knowledge for some time, but just now I took out some time to deepened my knowledge, and I've been had a doubt that could not find the answer searching the web.So, please, someone could give me a good definition of what "no-compromise AJAX" means? I can't figure out what this "compromise" referes about.If that is something obvious, please excuse me.Thank you a lot
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment