This post originated from an RSS feed registered with Agile Buzz
by James Robertson.
Original Post: Continuation based web apps explained
Feed Title: Cincom Smalltalk Blog - Smalltalk with Rants
Feed URL: http://www.cincomsmalltalk.com/rssBlog/rssBlogView.xml
Feed Description: James Robertson comments on Cincom Smalltalk, the Smalltalk development community, and IT trends and issues in general.
Avi Bryant pushes out a useful analogy for Continuation based web apps:
My argument is that this content or service view of the web doesn't scale up to the application level. It's like unix commands - it's nice that you can string together cat and sort and grep to do useful things, and that these provide services that anyone can take advantage of. But even though the loose coupling is great, you're going to have a real hard time writing emacs as a shell script. Or even pine. At a certain point, you need a richer model of state, of components, and of control flow. Building a complex application by stringing together a series of simple stateless parts, at the level of granularity we're talking about (essentially one user interaction per part), is madness.
Go read the whole thing. I'm not entirely certain that I completely agree (I'm more of the mind that HTML based apps suck), but he makes some very good points
Previous Topic
