> I've had at least 2 experiences with that particular tech, and I found it horribly over-engineered and a total PITA to work with. It's because XSL is (recurs

> I've had at least 2 experiences with that particular tech, and I found it horribly over-engineered and a total PITA to work with. It's because XSL is (recursive) functional programming, and most developers fight that fact trying to write imperative XSL. > We have HTML5 and CSS for rendering and JSON for content, and we should just leave everything else be. Except you're not going to anything with JSON without writing Javascript code, since neither HTML or CSS do understand JSON. XSL works without a single line of Javasript and it is still supported by most browsers.