Tuesday, March 14th, 2006
Real-World Ajax Seminar, New York
Category: Workshop
The Real-World Ajax Seminar just happened in New York.
Backbase’s Jep Castelein posted a summary of these talks:
- 8.50am – Jesse James Garrett
- 9.30am – Christophe Coenraets, Adobe
- 10.30am – Scott Dietzen, Zimbra
- 11.18am – Sahil Malik, Telerik
- 12.10am – Bill Scott, Yahoo!
- 12.30am – Lunch Break
- 13.38am – David Heinemeier Hansson, 37 Signals
- 14.38am – Jouk Pleiter, Backbase
- 15.46am – Kevin Hakman, Tibco
- 16.00am – Dave Crane, author of “AJAX in Action”
- 17.38am – Rob Gonda
- 19.05am – Time to go home
On Jesse-James Garrett (Adaptive Path, “Ajax”):
He explained how the term Ajax came about, and why he is so excited about Ajax, being based on web standards. He refers Ajax as ‘something we all make together’: it doesn’t belong to any vendor or any single person or company. To get the best usability, he suggests to take a multi-disciplinary approach, where people from different disciplines work together for the best results. He finishes with saying that the pioneers are now shaping the future of Ajax.
On David Heinemeier Hansson (37Signals, Rails):
…Then he continues with a bold statement: ‘JavaScript and the DOM still suck … a lot’. He emphasizes that there is a huge installed base of older browser versions, but you might want to focus on IE6 and Mozilla to avoid frustrations during development. He doesn’t like createNode(), and loves innerHTML() because it works consistently across browsers. He also likes eval(), the ‘small friend of innerHTML’.
On Kevin Hakman (Tibco):
Kevin gives a summary of his excellent article ‘Four quantum stages of Ajax’ which points out that Ajax can mean different things for different people. He identifies 4 levels: 1. Communication libraries 2. User Interface Components 3. Rich Internet Application frameworks 4. RIA Frameworks with robust visual tooling.
On Rob Gonda (iChameleon):
He is providing a lot of best-practices, such as ‘provide the user with immediate feedback’, ‘design for errors’ and ‘keep state on the server’. He explains that this last point is one of the most important points for enterprise Ajax applications, because it introduces security risks: he then primarily refers to business logic.
Related Content:
- Ajax is talk of the town in NYC
Jesse James Garrett, "Father of Ajax," and other luminaries in the Ajax world held forth yesterday in New York City. The optimistic consensus was that... - Ajax Learning Guide
Are you a Web developer? The time has come to rethink your entire approach to developing Web applications. Find out about the Ajax approach... - Ajax Learning Guide
Are you a Web developer? The time has come to rethink your entire approach to developing Web applications. Find out about the Ajax approach... - E-mail Security Seminar splash page
e-mail sec... - Security Events
4.8 rating from 45 votes
“Register Before
March 14, 2006 at
11:59 PM EST to SAVE!
These events are limited to 200 delegates!”
For those of who lives very far from the events, I have been searching for full text of the presentations. Thanks for the excerpts.
good speakers, good topics, good conference. I like to see conferences where you have visual designers, user experience, information architects, developers all in the same room, hopefully all learning from each other.
Correction, this event had 350 delegates on-site, and 15,000 viewers tuned in the simulcast.
Personally, having attended the event, I would think that David Heinemeier Hansson’s point about getting rid of duplicate presentation code by the means of utilising innerHTML is a very valid one. No one of us wants to build and then support rich internet applications that have one presentation layer for javascript enabled clients (by means of AJAX etc) and other layer for clients with javascript turned off.
The ideological “shift” from thinking of how to parse some propriatery XML data into nodes on the client (David made a point about “Nodes are not for people”) to just getting HTML (or XHTML) from the server and inserting that into your document with innerHTML, in my humble opinion, is something that we all should have a think about.
Providing HTML for non-AJAX capable clients and HTML for AJAX-capable clients just makes sense…
No podcast?
Mostly i like the way they providing a lot of best-practices, such as provide the user with immediate feedback.