Although I'd certainly like to get to the rapid part of cakePHP development, I'm not as concerned about the development time as I am concerned about production downtime. I do not have infrastructure to test code under load and for every possible query combination and software version combination (OS, DB, App, etc.). If the system crashes or does not scale for some reason, I would lose business while I searched the web looking for an resolution. I don't have years to become an expert in every little nuance. And, if I turn a profit with cakePHP, donations would be provided to the projects that support my business. Whatever technology I base my business on I want that technology to be reliable, sustained, and improved upon for years.
Anyway, thanks for your comments. -Reid On Jan 17, 12:38 pm, WebbedIT <[email protected]> wrote: > I am looking to move to CakePHP as my commercial solution and I have > shared the same concerns over my lengthy learning curve. > > I've submitted a lot of questions to this group and sometimes I have > had to resubmit the same questions in various different ways to get an > answer, but I accept that CakePHP is after all free (although those > using it commercially should really share a little love via donations) > and the support is in the main provided by it's users. Plus nine times > out of 10 the answer to my problems is simple and has been staring me > in the face for hours/days! > > The way I see it is CakePHP is a framework that you can use whichever > way you want, which in itself generates a lot of support queries, many > of which overlap, as people bend it in all sorts of directions to meet > their requirements. Whilst it is taking me a long time to learn how > to use the framework I know that as I grasp each concept the > convention over configuration principle means I can easily and quickly > apply it to all of my CakePHP projects (not that I have one project > finished). > > I am highly confident that my modest investment of time to learn this > framework will pay dividends as my previously bespoke PHP coded > applications that were really hard to maintain and update become more > streamlined and maintainable due to the conventions and design > patterns CakePHP uses, plus lead time of projects will reduce > drastically with each project as I will be able to reuse code I have > already written. > > But it comes down to what your requirements are at the end of the day! > > Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
