6. (thanx xkcd.com)

7. SEASIDE
Smalltalk Enterprise Application Server/IDE

8. SEASIDE
Squeak Enterprise Aubergines Server/IDE

9. >

13. 2007 goto?

14. href considered harmful?

15. href == goto?

19. Seaside
• Web app framework in Smalltalk
• Web app IDE in Smalltalk
• No hard-coded HTML links
• No pretty URLs

20. w hy s m a l l t a l k ?

21. f un

22. Power

23. powerful
continuations

24. Turtles all the way down

25. e di t smal l t al k
i n smal l t al k

26. con t i nuat i on
se r ve r

27. continuations?

28. continuations?
preserve all state
!
go somewhere else
!
do something else
!
all the state is there when you get back
!

29. Time Machine

30. State Handling In Web Apps

31. Normal Method
• Store state in the session
• Store state in the database
• Store state with flat files
• Obtain state from cookies
• Obtain state from CGI params

32. Seaside Method
• Application stores state in memory
• URLs have unique identifiers
• Implemented with continuations

33. How is it different
for the programmer?

34. Normal Method
• Access database
• Open flat files
• Read CGI params
• Read cookies

35. Seaside Method

36. Don’t think about
state at all

37. Just think about
your program

38. It kicks ass

39. To t a l l y d u d e

40. Rails makes Java and PHP
look like training wheels

41. Seaside makes Rails look
as if it has a speed limit

42. tedious

43. Seaside: ide = IDE
Debug your Web app in your Web app

45. explicit HREF statements

46. discouraged in Rails

47. impossible in Seaside

48. impossible in Seaside
(nearly)

49. href is goto

50. too much work

51. what does goto do?

52. s e n d yo u t o c o d e

53. what does href do?

54. s e n d yo u t o c o d e

55. why is goto
considered harmful?

56. p r i m i t i ve f l o w
c o n t ro l

57. why is href
considered harmful?

58. p r i m i t i ve f l o w
c o n t ro l

59. don’t be primitive

60. be advanced

62. impossible

64. Desktop app
developers
don’t have to
track state

65. Their frameworks do it for them

66. Their languages do it for them

67. Ours should too

68. Seaside does

69. Seaside has an answer

70. Not the answer

71. Rails has an answer too

72. Replace goto
with method dispatch

73. Replace href
with active resources

74. REST

75. supports

76. obsessed

77. REST

83. REST

84. ?

85. ...

86. Smalltalk:
Old School

89. Better Late Than Never

91. useless

92. funky

93. out there

94. weird

96. mind
expanding

97. nearly the same language

98. very similar syntax

99. ver y different contexts

100. Smalltalk Ruby
Unix
Virtual Machine
Windows

102. Turtles all the way down

103. e di t smal l t al k
i n smal l t al k

104. “Postmodern language”

105. “Postmodern language”
(glue language)

106. connect it to anything

107. have your cake
and eat it

108. ru b in iu s . . .

109. Still
just
one
of
many
possible
futures

110. Ruby vir tual machine

111. Turtles all the way down

112. e di t ru by
i n ruby

113. Seaside ported to Ruby...?

114. ...

115. REST

116. Heavy Light
CORBA JSON
SOAP REST

117. Light always wins.

118. people get involved

120. quot;Every developer working with the Web needs to read this book.quot;
- David Heinemeier Hansson, creator of the Rails framework

122. REST

123. REST
architectural style

125. REST

126. REST
Addressability
Statelessness
Connectedness
Uniform Interface

127. REST
Small, simple URLs

128. what if the Web was one
gigantic virtual machine?

129. <a href=“railsapp.com/controller/action”></a>

130. <a href=“railsapp.com/controller/action”></a>
monkeys.com/monkeys/feed
monkeys.com/monkeys/wash
monkeys.com/monkeys/elect

131. <a href=“railsapp.com/controller/action”></a>

132. <goto=“location/resource/action”></goto>

133. <invoke=“location/object/method”></invoke>

134. auto-generated goto statements

135. the Web is a virtual machine

136. Rails is a component compiler

137. (almost)

138. Seaside:

139. Seaside:
no almost about it

140. Seaside:
Web apps with state

141. Seaside:
no http gotos at all

143. ?

144. Giles Bowkett
gilesbowkett.blogspot.com
giles.tumblr.com