I've used Cake commercially for about two years now. Support may be an issue, but I have found this forum has answered most of my questions rapidly. The unanswered questions were usually about out-on-a-limb problems.
Two things are certain, though: 1. Using Cake dramatically improved development times. Maybe not for the first project where there was necessarily a learning curve, but for subsequent projects where drop-in reuse of functionality enabled a project to be fleshed out very rapidly. With each subsequent project, this advantage increases and permits better focussing on project specific functionality. 2. I see Cake almost as a language, or maybe a dialect, in it's own right - albeit one that can be fully customised with PHP. Before anybody jumps on me, I know this isn't true, but I now view work as either written in PHP or written in Cake. It is certainly not a replacement for PHP expertise nor is it a way to learn PHP. To use it, you need to know PHP and if you do, any problems you may encounter will not be insurmountable. I looked at other solutions and templating systems, and to be honest, without trying them all it was difficult to assess which may be best. I just had to jump in feet first. But at the end of the day what difference is there? Why choose Joomla over Drupal? Ford over GM or one girl over another? They all do what they were designed to do. I don't regret my decision. A question for you - why PostgreSQL? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
