I actually feel the opposite :) IMHO CakePHP is better suited for bigger projects, but it always comes down as to what developers like really. Just two days ago I did a stress testing of an application I built with Cake on two small servers: a LAMP on a Pentium 3 GHz, 2 GB RAM and on a WinXP, Apache2, PHP 5.1, Mysql on a Pentium Dual 2.6 GHz with 1 GB RAM and I was astonished with the great outcome (and believe you me, I was expecting a lot.)
When I said symfony lures I ment more the target that symfony seems to be after, not that it was something negative. When it comes down to development, semantics should not be an issue :) As to your PDF remark well you do have PDF manuals for cake as well. You've just gotta look for them: http://cakeforge.org/projects/cakedocs/ I use this PDF constantly while I'm developing just as you do with symfony's. One other thing about Cake is the active involvement of almost all cake's developers. How many times can you say you drop in your question on an eGroup and get almost immediate answers? Not that often, I imagine. I manage a Java Users Group for Latin America and it is not easy to find developers willing to help others. But I do agree with you. There's no black and white on deciding on a particular framework. Some people like Symfony better, while others enjoy working with CakePHP. It can be a number of things that make you decide on one framework over the other, from the most understandable (I need to keep supporting a PHP4 environment, or I like better Cake's approach to the MVC than that of symfony) to the most unusual ones (Cake just sounds way cooler than symfony, or I don't use Cake because I stay away from dairy.) -MI -----Mensaje original----- De: [email protected] [mailto:[EMAIL PROTECTED] En nombre de Bert Van den Brande Enviado el: Lunes, 13 de Noviembre de 2006 03:51 a.m. Para: [email protected] Asunto: Re: Cake PHP Vs Prado Vs Symfony I've been using both Cake and Symfony at the same time, and I think they are both great frameworks with some up- and downsides attached, which may not even be downsides or upsides depending on your point of view. Typically, it's all a matter of requirements and preferences ... while I believe it's true that Cake is great for quick development, I feel more comfortable with Symfony for a bigger project. Stating that Symfony is trying to 'lure' app developers into using it seems like sort of a negative remark that it don't deserves, as I do find for myself that Cake is missing some extensive documentation. To be practical: when coding in Symfony I have the Symonfy documentation in .pdf open all the time, and some quick searches usually lead me to the correct info in a matter of seconds. With Cake, I need to figure out the correct section of the online manual, and then most of the time I need to go to the google groups and hope to find some proper documented answers. As for the ORM part I am a strong supporter of Propel for years, but I also see the power of the Cake approach where lots of query results are at instantly available. One should of course take into consideration the extra load Propel-usage puts onto your application @ runtime, where on the other hand Cake is very lightweight. Cake's approach to convention over configuration is very good, and I also tend to dislike dozens of configuration files all over the place like you will have with Symfony. On a downside, Cake's documentation lacks some convention info which often has cost me valuable time trying to find out the reason for some behavior. So in the end, as I said, it's all a matter of requirements and preferences, and deciding what's best for your project ... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
