Thanks for the “great over all” :)

> Too long for medium

I agree. It was a hard decision, but at the end I decided to take the risk and go for the all-in-one article.

> The separation of concerns part is not fully developed imho

What do you mean? What the “separation of concerns” in web development means/meant (in that case, this old article by Jeremy Keith explains it perfectly), or what it means in the context of this “war”? I think that the illustration of how the two different parts are looking at it, speaks for itself. It’s not a problem of technologies or tools, it’s a matter of different “requirements” to satisfy, of different context of use of the same(-ish) tech stack.

> The critical question for me is: if I need to change the js logic is there a single piece to touch? What if I need to change an element of style?

In case of “atomic”, isolated components yes. That’s one of the main benefits of this approach (the modular approach, I mean). In this context the “HTML”/CSS/JS code for the different parts is co-located in the same file (generally speaking, I’m simplifying here).