silverlight - What are the main downfalls when using Google Web Toolkit (GWT) -
after long debate between many ria/ajax framework, settled on gwt. when reading it, framework seams doing , easy. technologies, there down side , we learn them hard-way.
what main downfalls or problems when using google web toolkit (gwt)?
(eg: back/forward button support, slow response time, layout positioning, javascrit bugs, etc)
so far, got following response:
- lots of code simple ui
- slow compilation
thank you
i have been using gwt 2 years. although called fanatic gwt, there issues 1 should know ...
as others have said, javascript compilation slow. application requires 4 minutes core i7 cpu, 8 gb memory. total size of generated javascript 5 mb. development mode, compilation javascript not needed frequently.
gwt rpc extremely slow in development mode. 100 times slower hosted mode. quite big problem us. did consider giving gwt because of reason. reason sluggish performance of gwt rpc in dev-mode serialization. serialization of types other string unbelievably slow in dev mode. did implement our custom serialization, 30 times faster gwt built-in serialization.
claims writing gwt application requires knowledge of java illusion. should have solid information css , dom. if don't, spend time debugging user interface.
you should consider can use small subset of jdk implement gwt applications. reflection not available; should use third party libraries, such gwt ent, or write own generator reflection.
another caveat 1 should consider size of generated javascript gwt compiler. of gwt applications consist of single web page, opposed multi-paged traditional web applications. therefore, loading of application requires significant time. although mitigated using multi-module approach , code splitting, using these techniques not straightforward.
all calls server asynchronous. should adapt writing asynchronous code. , downside of asynchronous code is more complex , less readable equivalent synchronous code.
Comments
Post a Comment