On Mon, Apr 30, 2012 at 02:57:39PM +0100, Matt Robinson wrote: > > Sure, but if you make a million+ dollar investment built on Symfony, you can > afford to pay for long term support from Sensio (or someone else). As far as > I know, they're still offering commercial support for 1.0 (at least I > remember Fabien saying something along those lines a while ago).
True (as also stated to Fabien). > The 3 year > support is what you get for free, not the _only_ thing you can get. Since > it's impossible to upgrade from 1.4 to 2.0, there'll be plenty of people > running 1.4 projects for many years to come. Which is my point also. > > And picking Symfony now is not easy, whatever you do you know you are > > going to have to change quite alot in short to middle term. > > Why are you going to have to change anything? You only need to upgrade if: >From building a 2.0 site today to the LTS wnehever that comes around. > 1. There's a security fix, but security fixes don't break compatibility. If the version you use is EOL, will the fixes be around? > 2. You aren't willing to accept community-only support, and aren't > willing/able to pay for commercial support. Since I am in some of the same business, there are willingness to pay when we see the need to pay. > 3. A plugin you're using is abandoned by its author, and then breaks (e.g. > something that consumes a web service whose API changes). But that's a risk > that applies regardless of how long Symfony itself is supported for. True as well. But the more time with the same API, the more development and stuff will be available for more people and it makes it easier to share out your own stuff without ending up with too much maintenance. A main reason for picking a framework is the vast ecosystem around it and the easier it is to use and be a part of that ecoststem, the better it is. Symfony is the Qt of web frameworks, look at it as that and it changes a bit. > We're confident enough that 1.4 will continue to be stable and useful for > the next 3-5 years that we're developing new sites for clients with it right > now. We tell our clients what the expected lifetime of a project is before > they start, so that they can see how long they can expect to be able to have > maintenance without a major upgrade. By picking 1.4 now you also deny yourself the possibility to use stuff our from the vild. That's OK for us developers earning money from making this but it's not always good for the customer. > After 5 years on the web, it's > definitely time to reevaluate the product anyway, A web framework does not have to be used "on the web" and there are web based systems made in the nineties still in daily use. And they even work. Thomas. -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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-devs?hl=en
