No, what you need is a descriptive language that gives designers what they want and then hook everything up by calling some stored procedures in a database. CRUD problem solved. :-) Or, maybe what you really need is a tight server code that then is hooked up by a dynamic front-end that often is a web-browser prone to all kinds of injection by those who know enough to be able to tamper with them. Making things like XSS attacks and targeted server requests possible, maybe by playing with your amazingly crafted JSON server APIs. Or maybe those static sites are looking all the more enticing, so just stay true to HTML of the 90s and generate just HTML/CSS and don't demand any JavaScript from the client. The thing about OOP is that when you fix the problem in one spot, you should be able to fix it for all the callers. So frameworks like Ruby on Rails by taking advantage of code-...