Thanks for explaining. Now I'm sure I disagree. :)

I'm partly kidding. I might use that design style under some circumstances. I disagree that it's the right way to do things. There are many ways to do things. I think people want a "right" way because they want to feel like they've got stuff figured out. (This is especially common in our world because software is complex and there's a lot of uncertainty around how to do it well.)

As it happens, the app I'm currently working on is as far away from this design style as you can get. We do almost everything in JS, even things that could easily be done in HTML and CSS. Our way of carving things up relies heavily on expressing everything in a single language, and the Turing-completeness of said language is an advantage not a disadvantage. It's a solution I'm fond of because it neatly combines high-level abstraction at the source level with some stringent performance requirements in the browser. It will also be fun to watch the purists turn green when they see it.

Edit: we do almost everything in generated JS. Might be relevant.