I hate to say this, but it feels like the same old arguments that people used for HTML in Java servlets, and then JSP/JSTL and then JSF and then Groovy and GWT and then… The “if everything is just in [language] it’s so much easier to [debug, code, pick-your-problem-du-jour].”
I get it, I really do, having fought with exactly what you’re talking about of a little change over here in HTML means digging through code over here in CSS and JS too and having this cascade. I’m just still not sold on “put everything in JS” as a long term solution to the problem. I also struggle with the reusability of things. One example is I have an address view and an address form but the data populating the view is different depending on where in the app I use it. In one place the data is from patient.addressLine1 and in another place the binding is member.address1. Do I just resolve that I have to have multiple address templates with different bindings or do I have to create some model methods that map my incoming model to what my template is looking for and how much code does that end up being.
The problem with people touting something as “evolutionary” or “game changing” as I’ve seen many people put this new/old step, is that it’s only provable at some point off in the future 3–5 years away. It needs time to mature and for processes to form around it and for tooling to catch up with the concept before we can call it anything other than “an idea” or “something you might wanna try out.”