I would describe it as "using JavaScript on HTML in a manner that fails to maintain separation of concerns, introducing pointless string processing overhead to the far simpler process of simply outputting markup or worse, encouraging the use of JavaScript on things that don't need or shouldn't use scripting. Much like "template systems" on other languages like PHP, it is pointless code-bloat used by people who don't know enough about HTML to be telling others how to build websites."
Much like react, or angular, or any of the rest of that nonsense, it's hot, trendy, and utterly pointless if you know the first damned thing about using HTML or JavaScript properly.
The only place it might have a use is full stack JS development, and even then if you're going to have scripting only elements build them on the DOM so you already have them hooked, instead of slopping around with XML-style templating rubbish.
But then my specialty is bailing out websites facing fines and civil lawsuits thanks to WCAG and other accessibility violations... and the way 90%+ of the people out there use JavaScript, well... the result is INSTANTLY looking at court time if used for medical, banking, utilities, or government agencies.
Ravindra Singh Shah
Raise > Recognise > Respond