This post originated from an RSS feed registered with Java Buzz
by Marc Logemann.
Original Post: Ajax - and why its dangerous
Feed Title: Marc's Java Blog
Feed URL: http://www.logemann.org/day/index_java.xml
Feed Description: Java related topics for all major areas. So you will see J2ME, J2SE and J2EE issues here.
First of all, Ajax is the worst acronym on the java market. In germany, Ajax is a cleaning agent. In the netherlands its a soccer club, but anyway. In every second blog and on conferenes like TSSS we hear that we can forget Swing now because we have this Javascript silver bullet now. To be more precise, Asynchronous JavaScript + XML. To be fair, filling combos without roundtrips is nice, but there is an inherent danger in this.
A lot of architects and developers are crazy and with the advent of Ajax, i see a lot of web applications hitting the streets (or better hitting the various companies) that never should be architected as web applications in the first place. I also see endless debugging sessions in open source javascript libraries and problems with browsers like safari. All this in applications which really should be written in Swing or C#/Winforms.
Ajax should be seen as what it is. Its ONE option to get a little bit more responsiveness and usability inside a WEB application.
Previous Topic
