3 ms·
js itself isn't so important. already the desktop UI approach (think Java AWT/Swing) is gaining traction, eg GWT. nonetheless, if using js directly, the js it
by InVerse 18y ago
js itself isn't so important.
already the desktop UI approach (think Java AWT/Swing) is gaining traction, eg GWT.
nonetheless, if using js directly, the js itself isn't so important:
* use a good js library with helpful abstractions for DOM traversal, manipulation, etc
* use good js frameworks, eg for compiling data plus templates into html
* use ajax to get html
- arockwell 18y agoDo you actually know anyone who uses GWT? I have not heard good things about it. I personally would rather ues plain javascript with jquery.
- litewulf 18y agoI actually use GWT, and my advice is to be very careful. I've managed to have bugs that show up in the browser that I have had an amazingly difficult time tracking down. You get a pile of javascript from your pile of java, and it can be hard to tell where the bug is at all. Complexity is dangerous, and GWT is fantastically complicated. I haven't run into a GWT compilation bug, but I'm sure there exists such a thing, and the day I run into it I will simply sit down and cry because I have no other recourse. (But when it works, I guess its kind of a nice way to build UIs, if you like Java-style UI APIs... I've never met such a person, but I'm sure they exist ;))
- Raphael 18y agoKdice.com, a game much like Risk, was done with GWT by one guy, and he wrote a book on GWT.