> -----Original Message----- > From: Argyn Kuketayev [mailto:[EMAIL PROTECTED]] > Sent: Thursday, June 27, 2002 9:32 AM > To: '[EMAIL PROTECTED]' > Subject: RE: Giving up! Cocoon too big, slow and confusing > > > Good post :) > > Wake up, guys! John raised a real issue. You can't simply say "Don't give > up, be patient, read mailing-list, look into sources..." and so on. If you > want this framework to catch the train, then there must be better support > and better documentation. > > I'm not complaining, by the way. I'd love Cocoon become a mainstream > framework.
I agree as well. It's nice when you have time to tinker, wait for useful replies from the mailling list or search the archives and wade through messages that most likely talk about version you're not using. It's nice to have time to look at source code and hope what you learn will still hold in the next version. Unfortunately, a lot of developers have very little time and don't want to spend all of their "well wasted time" on Cocoon. This is not about open-source vs closed-source, this about making Cocoon usefull to everyone. Yes, I know I can help by pathching, writing docs, answering questions on mailing lists (I sometimes do the last one), but that requires time that I, and many other developers, don't have. New features/design is nice but I'm already affraid I will have to go through same HELL moving from 2.0.2 to 2.1 as I did when moving from 1.8.x to 2.0.2. Please tell me that I'm crazy and that all I'll have to do is drop in a new jar(s) and edit my cocoon.xconf. I'm not crazy and I'll probably have to do a lot more and there wont be a migration guide to tell me what to do. Cocoon is great, cocoon developers/community is great, but I'm tired of explaining to VPs and clinets that Cocoon's benefits outweights its lack of documentation and API stability. These people would like to know that it will not cost them 3 months of extra development time, because their in house Cocoon expret was hit by a bus. So, IMO if you want Cocoon to succeed in medium/big business all you have to do is write lots of helpful docs. The upcoming books are a good start, but thinks like API JavaDocs with actual comments for each package/class/method and installation migration and user docs need to be released with each version. Artur... -- All I want is to use Cocoon. > > > -----Original Message----- > > From: John Austin [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, June 26, 2002 10:41 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED] > > Subject: Giving up! Cocoon too big, slow and confusing > > > > > > I'm back from a short vacation in beautiful Chicago (it > > really is much > > nicer than Toronto or Montreal) and have waded back in to > > Cocoon for a > > couple of days. > > > > After just a few hours of poking around I have decided that > > it will be > > much simpler for me to simply hand-code a whole hat-full of servlets > > than to try and pull any meaning out of Cocoon and it's documentation. > > Two days is absolutely not enough to get a grasp of Cocoon, definitely. > Unless, you are a twin brother of Stephano :) > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
