One of the primary reasons a company I worked for decided to use Vue was simply that the developers found it familiar. If you've been working with HTML and CSS

One of the primary reasons a company I worked for decided to use Vue was simply that the developers found it familiar. If you've been working with HTML and CSS already then Vue templates really just an extension to something you're already proficient with. This was important where I worked because we had frontend developers who built the components and pages, and content developers who didn't really touch much JS, but were responsible for small content and design contents around the website. They were able to work with Vue quite quickly because Vue templates are basically just HTML. All of these frameworks are really just making different tradeoffs in their approach. I don't think the author makes a bad point, but they are advocating for a very extreme position here without much concern for the trade-offs that are generally required to give a framework mass appeal and adoption. What they're suggesting would have simply been unworkable in the place I worked, for example. The hassle of reskilling just wouldn't have worth it simply so we could be content with the purism of our framework. JSX is ugly as hell. I like many hated it when it was first presented, but honestly, it works. It's not perfect, but that's actually a feature. It's why both new developers and senior developers and love and hate it for different reasons while still using it.