3 ms·

I think you're over-emphasizing the importance of the separation of business-logic. Essentially your templates shouldn't be making database calls, sure. But j

I think you're over-emphasizing the importance of the separation of business-logic. Essentially your templates shouldn't be making database calls, sure. But just because your template language is written in Python doesn't mean your templates are going to be making database calls. If the team is small and everyone knows Python well, I can see a pure-Python template system be far more advantageous than using a template language. Template languages are simply for designers anyway who don't understand Python (and don't need to). Good job on weby! Look forward to seeing the rest of the framework.

DrJosiah 16y ago
There is more to business logic than database calls. And there is more to modern web development than your backend language and your templating language (hello javascript, jquery, yui, mootools, etc.). Again, as I stated earlier, reducing the context switch time can help, and this may be low-hanging fruit for very small teams, but almost every Python programmer will be coming into this having used one of the big Python templating languages. And the moment you get a frontend person with usable jquery, yui, mootools, etc., experience, most of this "oh, try this new templating language that isn't like any other templating language you've probably ever used" is going right out the window; they are going to rewrite everything in the language of their choosing (it happened with our guy and django -> jinja, which was the right thing).