[Seaside] Re: website maintenance/feedback

[Sebastian Sastre]

adding some to the list (plus annotations):

- anthropomorphic approach. Very human-like way to program makes easier to install an interesting company culture
- "extreme short development and deployment cycles" <-- (often a week, depending on the feature a couple of days) this is extremely valuable to test business plans tweaks and getting more traction and social proof faster
- extremely productive & small teams <-- a 'pizza' team (a team you can feed using only one pizza) can run a whole startup.

"...
- small time-to-market;
- complex functionality;
- extreme short development and deployment cycles.

It is not optimal for startups having:
- extreme scalability or (real time) performance requirements;  <-- unacceptable (deal breaker) 
- existing libraries already covering most needed functionality.
For those startups Seaside can be suitable for proof of concepts. <-- kind of nice but... (opportunity here if you fix the previous issue)"

Notes about scalability:
Investors will not tell you no, they will tell you that they will think about it. So, anything that isn't a hell yeah is a no. So we better have that point addressed in a smarter way.

Said so, I'd add:

1 dabbledb found a way to make it work for them, nothing is written in stone saying they had to be the only ones (and if so lets break that stone)
2 if twitter runs on ruby, arguably slower than smalltalk VM's, then I feel that the can't scale judgment focused on theory and details and assumptions too soon
3 the wrong architecture (one that allows points of contention) will make even assembler to have scalability problems (reinforcing point 2)

I feel we can think bigger guys, is just addressing one issue at the time

sebastian

o/



On Feb 28, 2011, at 9:41 PM, Stephan Eggermont wrote:

> Sebastian wrote:
>> that list needs the profile that makes the whole difference:
>> - as investor
> 
> Yes of course. Something like:
> 
> The Seaside framework allows small teams to build (complex) web applications fast.
> It is interesting for startups needing:
> - small time-to-market;
> - complex functionality;
> - extreme short development and deployment cycles.
> It is not optimal for startups having:
> - extreme scalability or (real time) performance requirements;
> - existing libraries already covering most needed functionality.
> For those startups Seaside can be suitable for proof of concepts.
> 
> Stephan_______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110301/6433eeba/attachment.htm