[Seaside] Four proposals to improve Seaside
ramon.leon at allresnet.com
Mon Apr 20 17:34:46 UTC 2009
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of
> TheSmalltalkBlog at gmx.ch
> Sent: Monday, April 20, 2009 10:04 AM
> To: seaside at lists.squeakfoundation.org
> Subject: [Seaside] Four proposals to improve Seaside
> There are 4 new concrete technical proposals how to improve Seaside and
> one more comment on my blog:
> Comments and critics welcome!
What do you know, not one of them makes sense.
9. Seaside works with various web servers, WARequest is the adaptor they can
all use to work with Seaside. Your criticizing Seaside because you modified
Swazoo and duplicated code you also modified in Seaside. Absurd.
8, 7. Use Apache to serve up static content like every other sane person
and recognize that Seaside does it for development convenience, not for
handling production load that requires it to be insanely fast. The rest of
the world works with files and pathnames, and for serving web content and
staying compatible, so should Seaside.
6. You're over playing the accepted use of this "new" convention, yea, some
people do it and just as many don't. It's an issue of personal style, not
some big well known convention Seaside is ignoring. We have method
protocols for a reason, we don't have to duplicate them in the method names.
You want to know if something is a constructor, look at the protocol, not a
More information about the seaside