Web application architecture using XSLT

Good day habra people!

Being engaged in the development of web applications for a long time I was looking for ways to completely separate the form from the controller, i.e. exceptions to use php code or parody smarty in templates. Maybe he was looking bad, of course, but ... not so long ago he met xslt. He opened for me a new vision of architecture, or rather its implementation. Now I will try to describe what I mean ...

Previously, my view was processed by the controller, now the controller interacting with the model generates xml, which is subsequently processed by the parser or sent directly to the client.

With this work:
- the model and the controller are not dependent on the type and can be written in any programming language;
- as a parser you can use any library, also in any programming language.
- templates written in xslt do not depend on the way a web application is implemented.
')
Such an approach is convenient for multivariate implementations of web applications, some of which may be better implemented, for example, in perl, php, etc.

Questions:
- I would like to know from you, habra people, is it worth transferring xml or xml to the client?
- This topic is written because of the dispute about xslt templates and templates in the form of html + php, what do you think is preferable?
- Should I use this approach to implementation?

In this topic, I just wanted to share my view of architecture using xslt.
This is my first topic, thank you for your understanding ...

upd:
- based on this material, I will try to write an article with an example of the implementation of this approach.
- thanks for the understanding expressed in the minuses;)