Gwt tree style image plus full#
Gwt tree style image plus code#

Since then, others have appeared (CoffeeScript comes to mind, Dart is on its way, but also large JavaScript frameworks, the revolution of server-side JS with Node.JS and others, and a strong comeback for JavaScript as 'good enough' all-around language to be used not only on the client-side but also in other parts of your business stack.Īdditional Notes With Regard to your Original (Now Edited) Question About the Use of Firebug JavaScript has a great many pitfalls and oddities that you need to be aware of, and maybe it's just better to not even need to care about them. LESS/SASS were not that popular, jQuery was not yet the de-factory JS library, JavaScript libraries weren't spawned every other week, and tooling wasn't that great in general.īut, there already was a growing demand for professional and large web-applications with dynamic front-ends, so there was a gap to fill to make developers more productive.

But only a few years back, things were not so bright. The JavaScript world (and web front-end technologies in general) is extremely active these days, so things are looking up. Was a Good Idea at the Time: History Matters!! If you want most of the above but you just don't want Java, maybe look at Google Closure, or the Dojo Toolkit. But if it doesn't work for you, just use something else. It makes some people more productive and gives a good tool for non-JS developers to build professional web-apps with dynamic front-ends without touching (too much) JavaScript.

Gwt tree style image plus code#

You could very well also use some of Java's code quality tools on a GWT project (for source checks, not bytecode checks, as there isn't any). Using JUnit from within Eclipse IDE and from the command-line. GWT provides interesting libraries, and makes it easy (well, easier) to build I18N-enabled applications with dynamic bundle loading. It provides a good separation of concerns for large applications, with decent MVC or MVP architectures already pre-baked at your finger-tips.

Gwt tree style image plus full#

GWT writes faster and more compact JavaScript than you (for large applications),Īnd allows you to determine what gets sent to the client arguably more easily than with equivalent full JS solutions.

(Google Closure address that a bit while keeping the developer in the JavaScript world, if you prefer).

Documentation Generation: Sure you have JSDoc and a few others.

Continuous Integration and Continuous Inspection.

Unit-Testing: though that picked up over the last few years, it's also way more mature in the Java world.

Try to refactor JavaScript code on large codebases (say, 40K+ LOC) and weep.

IDEs: even if some IDEs support JavaScript, the level of support just doesn't compare.