@Chris I was thinking about having "the cms you can code anything upon it". This should of course not compete with the framework's own reputation, but increase it.
@Mariano Sorry but I do not share your elitist vision. Cakephp is making its best to reach new markets and to be used by the masses. Also I am rather considering the question of easing the processes in a team work, where we have various peoples with various skills. Most of our projects are starting small and growing later. We have a lot of legacy apps to manage and what we are producing will be managed by other peoples. We need to make the work easy for them, not require them to be super-geniouses to understand the mess we have produced. Sorry but I wont convince my managers by using your joda talk. :-) I just need something easy for them. The benefits are for me but I need to polish the caveats. Implementation speed in the early stages is one. CMSes seem faster to implement and therfore less costly for the agency. And they often claim to be usables as framworks. Mariano Iglesias wrote: > At the end of the day, CakePHP should not be aiming for the highest number > of developers, but for the best. Just because a bunch of people uses a > specific framework, that doesn't mean that is the best thing to do. IMO > developers who are serious about their job will not hesitate in choosing > CakePHP. > > That's what we should put our focus on. Only the best use the best. > > Sure, the foundation needs to sharpen its marketing strategy (that will > surely happen after the release of 1.2), but to change its way just to > convince someone who needs to see a particular tool, oh well, I say let that > someone walk away... > > When you, as an interested developer, judge a framework you should take into > consideration *NOT* how cute their website is, but: what is the community > behind it? what are its features? what does it offer me that other ones > don't? etc. etc. > > I think there are a lot of websites and web applications built with Cake to > give them an idea how flexible CakePHP is. Even the Cake team has produced > cake based applications (take a look at The Bakery). > > So if there's a group of people that want to build a Cake-based CMS then I > welcome that thought. But don't do it because you believe it is needed to > get *more* developers, do it because you believe in it (like gwoo would say, > sorry for the joda talk.) > > -MI > > --------------------------------------------------------------------------- > > Remember, smart coders answer ten questions for every question they ask. > So be smart, be cool, and share your knowledge. > > BAKE ON! > > blog: http://www.MarianoIglesias.com.ar > > > -----Mensaje original----- > De: [email protected] [mailto:[EMAIL PROTECTED] En nombre > de Chris Hartjes > Enviado el: Miércoles, 28 de Marzo de 2007 06:42 p.m. > Para: [email protected] > Asunto: Re: Proposal for "killer app" > > Won't this lead to CakePHP being labeled "the framework you can only > build a CMS with"? > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
