Art(h)ur discusses Ajax and its use in web development frameworks like Django. While Ajax is widely adopted, concerns about its implementation include file size, performance, generated markup, accessibility, and SEO. Django is praised for not shipping with a single Ajax library, allowing developers flexibility, though this is sometimes cited as a weakness. Loose coupling, hooks, and a library-agnostic approach can help address issues with Ajax implementations.

2. So who's this dude?
Art(h)ur
Working at Tesco Diets
Taming the unruly browsers
(more often the other way round)

3. http://slideshare.net/cistov

4. Not a 'how­to' talk

5. So, Ajax...

6. Clearly the most over­
hyped cleaning liquid ever

7. Say Ajax again!

8. Widely adopted

10. Ajax in broad sense

12. DRY

14. Django Goals

15. 1.Make web development
stupidly fast

16. 2. Automate the repetitive
stuff

17. 3. Practice loose coupling

18. 4. Follow best practices

19. 5. Be efficient

20. Pinax as 'Django with
bigger opinion'

21. But...

22. 'Django often gets marked down
in a "framework comparisons"
due to the lack of built in Ajax
support. Personally I think that
not shipping with a single
library is a feature, not a bug.'
Simon Willison

24. Giants & their shoulders

25. Fred

26. Exhibit A: ASP.NET UpdatePanel

27. Concerns:
Multiple scripts
Filesize
Performance
Generated Mark­up
Accessbility
SEO
Tied to specific library
Extension of built­in types

28. Exhibit B: Rails helpers

29. Concerns:
Generated Mark­up
Accessbility
SEO
Tied to specific library
Extension of built­in types

30. Exhibit C: Cappucino/GWT

34. Concerns:
Accessbility
SEO

35. If you have two separate
versions, this approach
may make sense

38. Chances are, you're not
building GMail though

41. http://leandrovieira.com/projects/jquery/lightbox/

42. Should I even be
bothered?

43. iPhone supports
JavaScript

44. Ok, slow JavaScript,
but still?

47. ¿Habla HTML?

50. <rant>

56. </rant>

58. “Just as easy as not to”

59. 3

61. Hooks

62. Clean HTML

63. Library­agnostic

64. Loose coupling

65. Drivers

66. Caching

67. Even back­end agnostic

68. Artur, this is all great,
but Ruby meet up is next
month

69. Meet 40 lines of messy
code

75. HttpRequest.is_ajax()
is your friend

84. Poor man's single­paged
applications

88. Dependencies

93. Providing configuration
data on page load

94. CSS classes?

95. Custom attributes?

96. data­* hell?

97. Inline objects?

99. Unit Testing

100. Extending functionality

101. Callbacks?

102. Custom events?

103. Inheritance?

104. Data Access?

106. XSS/XSRF & JSON APIs

116. GWT Query

121. Future?

122. Image Credits
http://www.flickr.com/photos/atauri/2358057325/
http://www.flickr.com/photos/jeffmcneill/4169128852/
http://www.flickr.com/photos/seandreilinger/3650862305/
http://www.flickr.com/photos/lrargerich/2800244229/
http://www.flickr.com/photos/mager/2803365394/
http://www.flickr.com/photos/joyoflife/317125573/
http://www.flickr.com/photos/young_einstein/74097753/
http://www.flickr.com/photos/drewm/4749504388/

123. Questions?
http://www.slideshare.net/cistov
http://www.twitter.com/cistov