[Seaside-dev] What is our Mission Statement?

[Sebastian Sastre]

> +1
> Examples:
> http://code.google.com/webtoolkit/makinggwtbetter.html
> http://wicket.apache.org/vision.html
> http://tapestry.apache.org/tapestry5.1/
> 
> > I am afraid, that if we try to satisfy everybody
> > we become indistinct.
> 
> It's not the indistinct that worries but we simply don't have the
> resources to do it and we'd lose focus.
> 
if we succeed in satisfying everybody we become plain mediocre not just indistinct. And as Philippe says, no resources to even try it.
Also I found those examples mediocres. We should not benchmark those. I can't read more than the first line of any of those without having to puke due to technical stuff. I don't want it to happen to the "seaside statement".
I know Seaside has everything to be much more than that.
Brutal truth: right now we suck because not only don't have one statment, we have like 3 to 6 rotating statments which, I'm sorry to the one who created it, comunication skill sucks or it's a genious if the goal is to succeed in confusing people about what the product is about.
The most powerful statement I've found is the one from Yukihiro Matsumoto made for ruby.
Matz said "Ruby is designed to make programmers happy."
No bullshit + big focus + no technical crap = huge spread capabilities.
If a statement like that can be created for seaside we'll have chances of being marketed decently. Otherwise the mission statement will born and remain invisible.
cheers,
sebastian

> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev