The Seaside web application framework is taken by storm. All major Smalltalk dialects have working ports of Seaside, contributing their particular strength to the mix. While Seaside itself tires to be dialect agnostic, vendors themselves are pushing in many different directions that are potentially incompatible. How does Seaside manage the compatibility among all these dialects? How does our dream Smalltalk vendor look like? How do we package the code in Seaside 2.9? And, most important, how does the future of Seaside look like?
Clipping is a handy way to collect important slides you want to go back to later.