by Lukas Renggli
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 tries 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 code Seaside 2.9? And, most important, what is the future of Seaside?
Bio: Lukas Renggli is expert in the development of Web applications and Content Management Systems. He is a core developer of Seaside. He is the author of Magritte, a framework to ease domain object modelling using meta-data, and Pier, a meta-described CMS entirely based on objects. Lukas Renggli is currently doing a PhD at the Software Composition Group, University of Bern, Switzerland. Lukas Renggli has given talks at various conferences.