[Seaside] Four proposals to improve Seaside

[TheSmalltalkBlog at gmx.ch]

Well, I begin to understand that Seaside was made only for such ingenious 
people - and that I am still ages away to be one of them and that I will 
probably never make it there.

9.  Your criticizing Seaside because you modified Swazoo and duplicated 
code you also modified in Seaside.  Absurd.

But even so great wise people like you sometimes don't read carefully and 
therefore don't understand what they read. You better read the comments on 
this post for more explanation! (You are 100% completely off the subject 
with your reply)



>             
> -------- Original-Nachricht --------
> Datum: Mon, 20 Apr 2009 10:34:46 -0700
> Von: "Ramon Leon" <ramon.leon at allresnet.com>
> An: "'Seaside - general discussion'" <seaside at lists.squeakfoundation.org>
> Betreff: RE: [Seaside] Four proposals to  improve Seaside
> 
>             > -----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:
> > 
> > http://thesmalltalkblog.blogspot.com
> > 
> > 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
> naming pattern.
> 
> Ramon Leon
> http://onsmalltalk.com
> 
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 
        
-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20090420/36aaa03d/attachment.htm