Ville Vainio wrote: > Yes, we're done and all in all it was remarkably easy (esp. compared to > my previous experience w/ plain old CGI). It's not that I don't dig the > TG way of doing things, it's just that I digged it enough to jump in > early and hence couldn't trust some of the options that would have been > more "comfortable" for us.
Yeah I know what you mean. I've been writing PHP commercially for nearly two years now, and TG is a breath of fresh air. It certainly makes a lot more sense than traditional approaches if you want to get something done fast. I don't know if I would use TG all apps, but I would definitely use it for a lot of apps in the future if I had the choice. Lack of reliable deployment without Cherrypy is a bit of a problem for selling it to my manager, but I have knocked up applications behind Apache with a reverse-proxy and no-one's noticed the difference (apart from "dude, why are you using tables for these forms?!") I think for performance or mission critical operations I would use PHP, but I'll be doing a lot of TG applications in the future. Performance will always be a big issue for me with TG until I run some real tests on it. I'm just finishing up an ad-server which would have been much more suited to Python, but performance was a big consideration. It would be nice if Python had as many web-oriented features in the standard lib as PHP, but PHP has always been designed for the web so that's not surprising. From now on, I always write background processes in Python if they do any real work. -Rob --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
