On Thu, 2007-02-08 at 17:31 +1000, Horst Herb wrote: > On Thursday 02 August 2007 07:04, iain duncan wrote: > > After that, it's really none of their concern which version of TG I use. > > If you enter a serious contract witha customer who knows what he is doing, > this is not good enough. > > I know the situation well enough from both sides (both as developer as well > as > employing contractors for projects) that long term maintainenace plays a > heavy role in all serious contracts, and demonstrating that long term > meintenace (eg security patches etc) is warranted is certainly a condition > without you won't sign any contracts with me. > > Frameworks that are under rapid development with ustable APIs are very nice > for proof-of-concept development, one-off quickies etc - but absolutely > unsuitable for serious deployment of long term projects UNLESS you are > prepared to put in the substantial extra maintenance work. > > Frameworks with stable APIs and lots of things going on under the hood are > fine in that apsect though - if I can do an easy_install -U ... and it > doesn't break my site, it's usable. Else, it's not.
I'm sure your attitude makes sense for your business niche. But, that does not mean that what is true for you is necessarily true for others. I do not contract to IT managers, I sell directly to small businesses. They hire me because I understand *them* and understand that they *don't* want to know what goes in code or what I use or how we deploy. They just want stable working solutions customized to their business model at a good price. The libraries in TG allow me to do this at a very good price to them. The maintenance cost of having to use a frozen python environment for their project is much smaller that the cost that would have been incurred by doing the same work in java or php. Their uprgade cycle is slow and they don't have any IT department that I need to coordinate with. The libraries we are using in TG are frequently 0.* releases. If you need to be able to update the global shared library anytime, that's a valid concern, but then IMHO you shouldn't be using TG in the first place. A framework using brand new tools is not a good fit for you if your number one priority is a stable api. Not a value judgement at all. I'm just pointing out that because that issue is a show stopper to *you* does not mean at all that it is necessarily a big deal to other clients. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
