I agree and I don't fully understand the why of it. I remember coding PL/SQL to emmit HTML in Oracle around 1999 or 2000 and using functions to code the vario

I agree and I don't fully understand the why of it. I remember coding PL/SQL to emmit HTML in Oracle around 1999 or 2000 and using functions to code the various elements. That got old and repetitive very quickly - for instance, everytime I had to correct a spelling error, I had to recompile the code. To get around it I used one or two tables to hold html snippets to decouple the business/backend logic from the frontend, and stopped using the PL/SQL functions completely. My speed of developmet skyrocketed, and separating and abstracting the frontend from the backend made so much sense. A few years later, I was doing web developemt with Python using the Zope framework (not many people know about it tiday, I think). It uses a specialised serverside templating language called TAL (Template Attribute Language)[1] that basically builds the front end dynamically, and then you feed it data from the backend. Very neat and allowed me to build reusable compoments as well as collections of a schema definition (basically a dict), html template(s) and the code to validate that the input matched the schema and could be rendered. Or something like that - its been 2 employers and almost 20 years since I worked with that :) I did build a small extension for Wordpress using a PHP implementation[2] of TAL a few years ago, and TAL still works like a charm :) My point is that I still believe there is value in keeping python out of the html-templating, and in keeping the front end logic apart from the backend logic. There is something I am not understanding about the renewal of mixing HTML/GUI template with code, but I haven't fully found it yet. [1] https://en.m.wikipedia.org/wiki/Template_Attribute_Language https://en.m.wikipedia.org/wiki/Template_Attribute_Language [2] I believe it was this one https://phptal.org/ https://phptal.org/