Thanks for the response! It’s very appreciated.

I take your point about maintainability with regards to a designer editing the html. I’ve only worked for quite small organisations (<100 employees) so I’ve never really seen a designer do any coding at all. I get pictures from my designers :D

WRT your point about decoupling logic from markup, I disagree. There’s no difference in effect between v-for and map(). Both are presentation logic and both are declarative in nature. My argument really is that the v-for approach is just unnecessary because map() is a nice clean functional approach already contained in javascript.

Also, mapping data structures to element lists just *feels* right to me. In the traditional functional sense I *am* mapping a data structure directly to a html element in a 1 to 1 manner so why not use the correct tools for the job?

Ultimately, Vue does the same thing in the sense that it maps props to html elements. React just skips a whole bunch of (in my opinion unnecessary) abstractions.