Hello all, I''m hoping that someone out there in Rails-land has developed in both Cocoon and Rails and would like to share their experiences using both application frameworks. I''m going to be doing a presentation in the next couple of days on the advantages that Rails affords. The higher-ups are going to use this info on deciding whether or not to move away from Cocoon and I''d like to present some first hand information on the advantages/disadvantages of making the switch. Thanks in advance for your help. Mike
Advantage: You won''t have to code in XSLT any more :)
Erik
On Sep 19, 2005, at 1:31 PM, Mike Elkink wrote:
> Hello all,
>
> I''m hoping that someone out there in Rails-land has developed in
> both Cocoon
> and Rails and would like to share their experiences using both
> application
> frameworks.
>
> I''m going to be doing a presentation in the next couple of days on
the
> advantages that Rails affords. The higher-ups are going to use
> this info on
> deciding whether or not to move away from Cocoon and I''d like to
> present
> some first hand information on the advantages/disadvantages of
> making the
> switch.
>
> Thanks in advance for your help.
>
> Mike
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
On Sep 19, 2005, at 1:31 PM, Mike Elkink wrote:> Hello all, > > I''m hoping that someone out there in Rails-land has developed in > both Cocoon > and Rails and would like to share their experiences using both > application > frameworks.First of all, web applications are a second thought for Cocoon. It is attempting to morph itself into a web application framework, and it ain''t as pretty as a caterpillar becoming a butterfly. I''m no genius, but it took me almost a week of reading to figure out what I was supposed to *do* with Cocoon. It is a processing pipeline. Okay, and I need one of those why? Rails, on the other hand, is written to make generating strings as easy as possible. You can literally begin using it in a couple hours - less if you run on Mac OS X. It is much easier to understand, as it embraces the environment it was written to run in. It makes you feel smart. Cocoon made me feel stupid. adam
I started looking at Cocoon before the 2.0 restructuring. After the restructure I decided to give the 2.0 version a try. This was a horrible experience. The major thing I took away from Cocoon is that it was yet another processing layer. So, with Apache, Tomcat and then Cocoon it seemed like a ridiculous construct for web development. This was actually the beginning of my dislike of JAVA and the ever growing bloat associated with trying to make things easier. A former colleague of mine had a pattern for this which he called composting. Basically meaning that layers are added over the code base to handle its shortcomings eventually resulting in a big pile of crap. -- Andrew Stone _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
Judging Java by Cocoon is not quite fair. Cocoon is a specialized
framework with great strengths in the XML transformation pipelining,
and it really shines in this area. Many large corporations have done
very well with Cocoon for content management systems that lend
themselves to publishing of content to various formats. It
originally lacked decent interactive web application capability, but
that has been remedied and Cocoon now sports continuation-based flow
control.
I''ve known many who have had success (and even pleasure!) from using
Cocoon.
Personally I dislike XSLT, though, so it isn''t a good fit for my
tastes, nor have the applications I''ve worked on lent themselves well
to Cocoon''s strengths.
So while my first comment about Cocoon was perhaps taken negatively,
I think understanding the purpose and strengths/weaknesses of a
framework is important to understanding how to compare it to other
frameworks.
Comparing Rails to Cocoon is a bit like comparing a cat to a dog.
Which is cuter? Which is bigger? What you answer depends on the
question asked.
Erik
On Sep 19, 2005, at 11:30 PM, Andrew Stone wrote:
> I started looking at Cocoon before the 2.0 restructuring. After
> the restructure I decided to give the 2.0 version a try. This was
> a horrible experience. The major thing I took away from Cocoon is
> that it was yet another processing layer. So, with Apache, Tomcat
> and then Cocoon it seemed like a ridiculous construct for web
> development. This was actually the beginning of my dislike of JAVA
> and the ever growing bloat associated with trying to make things
> easier.
>
> A former colleague of mine had a pattern for this which he called
> composting. Basically meaning that layers are added over the code
> base to handle its shortcomings eventually resulting in a big pile
> of crap.
>
>
> --
> Andrew Stone
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>