Comments on: Seaside and Smalltalk Interest Spreading http://onsmalltalk.com/programming/smalltalk/seaside-and-smalltalk-interest-spreading/ thoughts on Smalltalk and programming in general... Fri, 16 May 2008 05:29:36 +0000 http://wordpress.org/?v=2.5.1 By: Ramon Leon http://onsmalltalk.com/programming/smalltalk/seaside-and-smalltalk-interest-spreading/#comment-427 Ramon Leon Fri, 08 Dec 2006 16:34:31 +0000 http://onsmalltalk.com/programming/smalltalk/seaside-and-smalltalk-interest-spreading/#comment-427 It's a common misconception that we don't have version control, we do, and it's quite a bit nicer than version control based on text files. Look at Seaside itself, it's an open source project where many developers work on and merge code constantly, works great. Most load balances have the options to stick a session to a server, since sessions are a common requirement among many frameworks. Seaside isn't stateless, so no, it won't scale the way a stateless server does, nor is it meant too. It's meant to write complex stateful "applications", not just websites, that have lot's of workflow and would be hard or impossible to write otherwise. However, don't think it won't scale, it's simply a matter of hardware. It’s a common misconception that we don’t have version control, we do, and it’s quite a bit nicer than version control based on text files. Look at Seaside itself, it’s an open source project where many developers work on and merge code constantly, works great.

Most load balances have the options to stick a session to a server, since sessions are a common requirement among many frameworks.

Seaside isn’t stateless, so no, it won’t scale the way a stateless server does, nor is it meant too. It’s meant to write complex stateful “applications”, not just websites, that have lot’s of workflow and would be hard or impossible to write otherwise. However, don’t think it won’t scale, it’s simply a matter of hardware.

]]> By: Wes http://onsmalltalk.com/programming/smalltalk/seaside-and-smalltalk-interest-spreading/#comment-426 Wes Fri, 08 Dec 2006 16:25:51 +0000 http://onsmalltalk.com/programming/smalltalk/seaside-and-smalltalk-interest-spreading/#comment-426 I've always found Seaside to be compelling, but I've always wondered, how can multiple developers work on code when the language is VM based? (I'm used to version control systems..) Also, application scaling seems to be an issue. From what I read, a load balancer like Pen must be used, in order to ensure that a user always returns to the application instance that they first visited. (Most load balancers distribute the load evenly). Is this as big an issue as it seems? I hate to bring up scaling as it is often used against dynamic languages, but it seems to me that the next myspace killer won't be developed with seaside. However, Seaside does seem to be well suitable for business oriented intranet apps. I’ve always found Seaside to be compelling, but I’ve always wondered, how can multiple developers work on code when the language is VM based? (I’m used to version control systems..)

Also, application scaling seems to be an issue. From what I read, a load balancer like Pen must be used, in order to ensure that a user always returns to the application instance that they first visited. (Most load balancers distribute the load evenly). Is this as big an issue as it seems? I hate to bring up scaling as it is often used against dynamic languages, but it seems to me that the next myspace killer won’t be developed with seaside. However, Seaside does seem to be well suitable for business oriented intranet apps.

]]>