<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 14, 2014 at 8:29 PM, tim Rowledge <span dir="ltr"><<a href="mailto:tim@rowledge.org" target="_blank">tim@rowledge.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br>
On 14-01-2014, at 5:17 PM, Colin Putney <<a href="mailto:colin@wiresong.com">colin@wiresong.com</a>> wrote:<br>
> Meh. Don't worry about it. Seaside is obsolete anyway.<br>
<br>
</div>Really? I haven’t taken any interest in web development in ages; what’s the replacement for Seaside?<br></blockquote><div><br></div><div>It's not that there's a replacement. It's more that the problem it solves isn't a problem anymore. Continuations were a brilliant way to manage apps that were basically dynamically generated web pages connected via links and forms. But Javascript runtimes have gotten way, way faster, more robust and more standardized in the last 10 years. Modern web apps are more of a client-server model: the UI rendering and interface logic is all done in Javascript running in the browser, and it communicates with the server by shuttling JSON back and forth over HTTP. In that sort of a system, continuations don't provide any benefit, and the drawbacks start to become significant.</div>
<div><br></div><div>Colin</div></div></div></div>