Hi Peter, > > Actually, I think that's a bad idea. Front-to-back frameworks are all > about consistency and One Way to Do It.
That doesn't imply either we talk about the implementation or the design. WSGI is a not about the implementation but the design, still it's One Way to Do It. By encouraging pluggable > components, this concept would be ruined, IMO. > > Sounds like you want to write a CherryPy generic template API. Nope, but CherryPy core idea is to stay out of the way of the developer as much as possible. If people keep writing new web frameworks, it's exactly because at one point you try many of them and you think "damn it no let me work the way I want. Screw it I'll write my own". If you make sure people can use their template of choice, their backend of choice, etc. then you make sure people are happy because they don't have to learn a new framework all over again each time. But fair enough, Kevin said it was not his priority and I respect that (and I respect your POV of course), I just think that sooner or later someone will write a TG killer framework because he work the way he wanted with TG. - Sylvain ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
