> Now it looks as if the open source world is going the same way. It > does not help my cause when I selll my customers on this wonderful new > package called Turbogears that uses SQLObjects, Cherrypy and Kid > templates.
You don't actually, we will be supporting TG1 for at least the next year. > Now before we have even finished the project I have to go > back and say sorry, we got that wrong, it is now SQLAlchemy, Pylons > and Genshi templates. But don't worry if we add Elixir as well, we > can make SQLAlchemy look like SqlObjects! To move to to turbogears2 you don't have to change SQLObject out at all, nor do you have to change kid. You want stability, and we are working hard to provide that. TG1 will remain supported for a long time, which isn't set in stone mainly because it's determined by how many people want that stability. But others, want to have access to new and better tools, and we are working hard to provide that too. TurboGears 2 is a new package, with a new name, and can be installed alongside the old turbogears 1 package with no problems and no conflicts. So, you can run both on the same server at the same time, and you can migrate your apps as appropriate to your own needs (if you find you need SQLAlchemy, migrate). At the same time we've worked hard to make it easy to migrate -- because we have to migrate our own large applications too! :) > The dumb customer, who does not have religious convictions about > which is the best web server interface, I hope you're not calling your customer dumb on a public maling list! Ouch. > asks me what is the advantage to him of making all these > changes? Any ideas? There are lots of advantages to each of the changes, but the nice thing is you don't have to make any of them if you don't need them, and you can switch to Genshi in TurboGears 1.0.3 with no problems, so if you just want that one you're good to go. The same goes for SQLAlchemy. If on the other hand you want Pylons integration, but you want to keep Kid and SQLObject you can do that by moving to TG2. We're putting you in the drivers seat. You get to control when, how and if you make these changes. All we're doing is creating a new default set for new projects that includes the newer components with all the advantages of these components. > People never seem to learn that "if it ain't broke don't fix it". Of course, if we never "fixed" anything that wasn't "broken" we'd never learn to do something better than we did before. Web development isn't a static space, and we (like everybody else) are trying to make it a better place -- and that means change. We're maintaining as much backwards compatibility as we can, creating migration paths, and doing what we can to make developers lives as easy as we can. But if we don't continue to pay attention to the best tools available and continue to innovate, we'll quickly become an irrelevant has-been technology, and leave our users in a dead-end. That's certainly not what anybody wants. So, we have to cut a path between total stability and maximum innovation, and we're trying to do that in a clean way. But we're also smart enough to know that we should give each of our developers choices about what path to take for their own application. That's why TG2 will support Kid and SQLObject, and TG1 supports Genshi and SQLAlchemy already. We're not perfect, so if you have some specific suggestions on how to make your life easier as we move forward, please let us know, and we'll do our best. -- Mark Ramm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
