> > Is STAN useful to Turbogears? Mabye.
But I feel like the real question is: Should Turbogears support STAN "out of the box"? I'm hoping for "no" on this one. One of TG's most valuable assets is its roadmap. New adopters can skim the docs and walk away thinking "learn slqobject, kid and a little cherrypy." and be on track. This, in my opinion, is a really good thing. Asking people pick a view technology (kid, stan or otherwise) before they have any information on how to make that decsion will only lead to confusion. And confusion leads potential adopters directly to Rails. Python has plenty of really excellent web tools. Nonetheless, web development with python is still a fragmented, daunting endeavor. Our community doesn't have a strong alternative to Rails. We're missing a uniform, well documented, hyper-productive framework that ties it all together. Enter TurboGears (I hope). As a side note, I really like STAN. In fact, I'm sure I'll end up using it because a) kid just hasn't clicked for me and b) I've never worked with a designer that could produce production ready html. But I'm not a new adopter. The great news to me is that I can make this choice because TG doesn't stand in my way. I do think MochiKit's use of STAN is very interesting. Maybe the real question is "Should STAN replace kid?". So I guess the real bottom line is "There can be only one!" is more important than "STAN Rocks!". If I had the freedom to pick a replacement for kid, it would be STAN. - Levi
