Interesting.. Do you know the reason they don't want to use symfony? is it because they want to maintain the application themselves? or with labour cheaper than yourself once it's built? it would be interesting to know... as it could spur on a symfony and TCO study or something.
I actually find that it takes me considerably longer to do anything when not using symfony now... validators? security? ORM? ergh. Even simple CRUD applications can be knocked out quickly - remember the original Blog screencast for 1.0? how long did that take? 8 minutes or so? The only argument I can see against using symfony is for the reasons I mentioned above. On 1 Nov 2009, at 18:34, Derrek wrote: > > > I've learned as a consultant that it's not worth trying to convince > people to use symfony. Some people are simply content in a short > sighted only do enough work to solve the immediate problem mentality. > That's fine, and for many smaller projects, it works fine too. > > I have a number of clients that have resisted the move to symfony or > frameworks like it. It has literally cost them hundreds of thousands > of dollars as now they need much of what symfony has to offer but are > stuck in a non-symfony world where making these kinds of changes > requires months of work. > > On the bright side, much of that money ends up in my pocket. ;) So, > really I use symfony on my own projects to give me a technical > advantage. But if a client doesn't want symfony, I'm happy to take all > the extra money they will spend to compete with others using > symfony. ;) > > --Derrek > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" 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/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
