3 ms·
> People end up writing things like: for (x in hugelist) { doSynchronousCall() What are you referring to here? I use client-side GWT daily; it is clear that RP
by justinmk 14y ago
> People end up writing things like: for (x in hugelist) { doSynchronousCall()
What are you referring to here? I use client-side GWT daily; it is clear that RPC success() and failure() callbacks are asynchronous.
> the JavaScript world has moved extremely fast in the 4 or 5 years since GWT was developed ... So they're locked out.
GWT uses the Closure compiler, which presumably takes advantage of modern javascript advantages.
> when generating JS it just leads to UIs that crash the browser.
I work on a very large GWT client-side application, and size is indeed becoming a problem. Java is like kudzu.
- chubot 14y agoOK I guess I'm misinformed -- all I'm saying is that I've opened up a bunch of GWT applications in firebug / chrome developer tools. And I see lots of multi-second latencies and dozens or even hundreds (!) of round trips to the server. Which makes it clear to me that the developers don't understand what they are actually writing. I'll admit to being wrong on that one point, but I was upvoted like hell so I guess other people have the same impression of GWT that I do.
- drivebyacct2 14y agoServer calls != synchronous... Why is this being downvoted? Calls to the server to update state do not have to be synchronous and it's fairly obvious that this is a mistake the parent poster is making in his obnoxious claims against GWT.
- johnyzee 14y agoConsider GWT's code splitting when the codebase starts to become large: https://developers.google.com/web-toolkit/doc/latest/DevGuideCodeSplitting https://developers.google.com/web-toolkit/doc/latest/DevGuid...