3 ms·
I have used GWT extensively and like it a lot. You are approaching the problem from the perspective of deploying a new web-application. GWT is good when you a
by tezza 17y ago
I have used GWT extensively and like it a lot.
You are approaching the problem from the perspective of deploying a new web-application.
GWT is good when you are approaching from an existing service and web-enabling it.
---
Further, some people like compile-time checks and the sophisticated IDEs.
With statically typed languages you can easily build an exhaustive list of all uses of something, where as dynamic/functional is much harder.
This makes changes and refactoring easier IMO.
- swolchok 17y ago>With statically typed languages you can easily build an exhaustive list of all uses of something, where as dynamic/functional is much harder. This makes changes and refactoring easier IMO. This is not guaranteed in Java and C# -- someone might have used reflection somewhere. http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.ht...
- hello_moto 17y agoReflection is usually kept at minimum at most libraries and systems. Those reflection codes are also self-contained in most cases (transforming from one object to the other, etc). So all in all, refactoring is still a lot easier. Furthermore, GWT takes out Java reflection.