Return-Path: Delivered-To: apmail-jakarta-struts-user-archive@jakarta.apache.org Received: (qmail 29959 invoked by uid 500); 28 Aug 2001 19:44:00 -0000 Mailing-List: contact struts-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: struts-user@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list struts-user@jakarta.apache.org Received: (qmail 29943 invoked from network); 28 Aug 2001 19:44:00 -0000 Received: from unknown (HELO toto.research.aa.wl.com) (162.48.100.19) by daedalus.apache.org with SMTP; 28 Aug 2001 19:44:00 -0000 Received: by toto.research.aa.wl.com with Internet Mail Service (5.5.2653.19) id ; Tue, 28 Aug 2001 15:43:36 -0400 Message-ID: <6944FBE0F687D411823D00508B6095FA0426BFEE@aaunderdog.research.aa.wl.com> From: "George, Carl" To: "'struts-user@jakarta.apache.org'" Subject: RE: Barracuda vs. Struts (request for review) Date: Tue, 28 Aug 2001 15:43:35 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Your not making anyone (if a may speak for everyone) mad, your just wrong! -----Original Message----- From: Christian Cryder [mailto:christianc@enhydra.org] Sent: Tuesday, August 28, 2001 3:28 PM To: struts-user@jakarta.apache.org Subject: RE: Barracuda vs. Struts (request for review) Hi Chris, Yeah, upon re-reading I definitely can see your point. Certainly not my intention to demean anyone. And, upon further reflection, I probably need to qualify my statements about Struts' target audience as well...let's see if you find this any better: -------------- The Barracuda Presentation framework is built as a series of layers that depend on the Servlet 2.2+ API, each of which can be used independently of one another. In terms of audience, Barracuda definitely aims at the Java Developer end of the spectrum (with the idea that tools integration will ultimately make the approach more accessible to Page Author types). ...... Unlike Barracuda, Struts is aimed primarily at the Page Author types. This is not to say that Struts does not require Java coding--after all, you still need developer types to implement Tag libraries and write Controller code. Rather it aims to suggest that it is Page Authors who will get the most mileage from the framework; if you do not adopt a JSP strategy for rendering views, the value of Struts is greatly diminished. -------------- Does this help at all? Or am I just making everyone mad? I'm not trying to demean Struts or Page Authors here, but rather to illustrate a subtle-yet-significant (in my mind at least). It seems to me that Struts doesn't offer a whole lot for those who don't want to go the JSP route. This seems to be evidenced by the fact (at least in my perception) that there are not many people using Struts who are not ALSO using JSPs. This is not necessarily a bad thing, after all, the converse is equally true--Barracuda doesn't offer much if you ARE committed to JSPs. I'm just trying to explain why I feel that Struts is more oriented towards page author types. Christian ------------------------------------------------ Christian Cryder [christianc@enhydra.org] Barracuda - MVC Component Framework for Webapps http://barracuda.enhydra.org ------------------------------------------------ "What a great time to be a Geek" > -----Original Message----- > From: Assenza, Chris [mailto:cassenza@Accessdc.com] > Sent: Monday, August 27, 2001 1:34 PM > To: 'struts-user@jakarta.apache.org' > Subject: RE: Barracuda vs. Struts (request for review) > > > I haven't read it all yet (and would like to - Barracuda looks > intriguing), > but: > > "Barracuda definitely aims at the Java Developer end of the spectrum (with > the idea that tools integration will ultimately bridge the gap to less > sophisticated Page Author types)." > > ... > > "Unlike Barracuda, Struts is aimed squarely at the Page Author types" > > "Less sophisticated" sounds really arrogant, demeaning and is > clearly biased > - and that's not even the meat of the presentation. :p > > Don't get me wrong, I'm not offended nor do I think anyone should be, but > that tone so early on changed my perception almost instantaneously. There > are better ways to say what you are trying to communicate IMO, and little > phrases like that really do count. > > Best, > > -Chris > > Christopher Assenza > Phone: 412.201.6026 > Fax: 412.201.6060 > Email: cassenza@accessdc.com > ACCESSDATA > Moving Your Business from Point A to Point e.SM > http://www.accessdc.com/ > > > > -----Original Message----- > From: Christian Cryder [mailto:christianc@enhydra.org] > Sent: Monday, August 27, 2001 3:31 PM > To: Struts-User > Subject: Barracuda vs. Struts (request for review) > > > Hi guys, > > I've put together a fairly detailed architectural comparison of Struts vs. > Barracuda: > http://barracuda.enhydra.org/cvs_source/Barracuda/docs/barracuda_v s_struts.h tml While I've tried to keep the document fair and even-handed, it's quite possible that I've not given Struts a fair shake (since I don't know Struts that well after all). At any rate, I wanted to give you Struts experts a chance to review the document and correct any misunderstandings I might have. If you think I've really botched something, please let me know and I'll try to make it better. My goal here is to represent both frameworks as accurately as possible. Thanks much, Christian ------------------------------------------------ Christian Cryder [christianc@enhydra.org] Barracuda - MVC Component Framework for Webapps http://barracuda.enhydra.org ------------------------------------------------ "What a great time to be a Geek"