4 ms·
In my view, GWT is for creating large/robust web-based applications, and that is where machine-level optimizations really pay off. If you are writing a tiny ut
by ttcbj 15y ago
In my view, GWT is for creating large/robust web-based applications, and that is where machine-level optimizations really pay off. If you are writing a tiny utility on a page, hand coded javascript might pay off, but if you are writing a large/complex application, it becomes impractical for a human to do what a optimizer can.
I am not saying that GWT is perfect for everything, but it pains me to think of writing (and debugging, and refactoring) a large application in javascript, or any weakly typed language. I've tried it, and found it difficult to maintain.
- rbanffy 15y agoIs there a good definition of "robust" in this context?
- oelewapperke 15y agoMore than thousand lines ? Javascript becomes a disaster to read or maintain. Tools like Jquery help, but not enough to make it usable. Javascript is like perl. And, frankly, Java is not. You can actually manage a huge Java application (and you can even have the work done by barely-competent programmers, which is a plus). There is no way to have 50 programmers working on a 50000 line javascript app.