Hey Terrence -- > This is what I used to think, but something very similar to > CGI::Application is coming out for Mason soon, here is a recent > post from the Mason list:
Soon? What kind of FUD is that? CGI::Application exists NOW! Hehe.. Seriously -- if you read that message from the Mason list you will see that a single Mason developer is about to re-invent CGI::Application. I've taken the liberty of posting a message to the Mason mailing list (and to John Siracusa) inviting him to check out CGI-App. I have two thoughts about what John is doing: 1. Creating a bridge between CGI::Application and HTML::Mason is a reasonable idea, and one which would not be very hard to implement. 2. Nobody will use it, except for you, me and John. I would like to be wrong about that second point, but I fear that Mason users are not interested in this architecture. Their projects are mostly sites which consist of hundreds of homogenous pages with light-weight, relatively uncomplicated functionality. Their developers are mostly generalists. They have accepted the nightmare of resolving conflicts between code changes and HTML design changes. In fact, most of them don't believe there is any other way! I think the fact that the most sophisticated Mason users are coming around to see that an architecture like CGI::Application is necessary, says something. It shows that sooner or later, IMHO, it will become common sense that both systems are necessary. For me, I continue to choose application-oriented architectures because server-page architectures make my eyes bleed! Since avoiding unnecessary pain and suffering is my primary interest, systems such as Mason or Cold Fusion will be, for me, no more than an occasional necessary evil. -Jesse- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
