- could share validation logic between front end and back end
Bad bits:
- abstraction broke sometimes. I remember one bug that drove me crazy--only showed up when I deployed the optimized code (vs the detailed code which was human readable), and was due to a namespace collision with a global js variable.
- compilation was another build step and sometimes not a quick one.
- far better for full page applications than drop in js widgets (we used it in both ways)
Overall I think it was a great solution for its time. Now a lot of the JavaScript ecosystem has caught up or surpassed it.
Good bits:
- abstraction from different browsers
- ability to set breakpoints and debug code running in browser (browser based tools were not so full featured as they are now)
- refactoring
- Java code organization (packages, classes, interfaces)
- could share validation logic between front end and back end
Bad bits:
- abstraction broke sometimes. I remember one bug that drove me crazy--only showed up when I deployed the optimized code (vs the detailed code which was human readable), and was due to a namespace collision with a global js variable.
- compilation was another build step and sometimes not a quick one.
- far better for full page applications than drop in js widgets (we used it in both ways)
Overall I think it was a great solution for its time. Now a lot of the JavaScript ecosystem has caught up or surpassed it.