Wasn't exactly my point, it's the criticism of JS the language and the tooling, but then just repeats the same difficult to maintain approach seen in a lot of JS, but now in a new language and even more tooling

This is what exploring the envelope looks like. New wasm stuff is going to look like hot garbage until new sets of abstractions and new conventions start to shape up. There’s a lot of ground to re-explore and re-cover before wasm starts punching at its weight.

You know something has to perform low level DOM operations, right?

Sure, but I was under impression that it's best left to the C++ the browsers are written in?

The browsers written in C++ are not doing DOM manipulation, they're providing the DOM abstraction itself.

Using innerHTML kind of is leaving the DOM manipulation to the C++ the browsers are written in!

Using innerHTML is leaving the DOM manipulation to the C++ the browsers are written in.

Using createElement is leaving the DOM manipulation to the C++ the browsers are written in.

Using HTML is leaving the DOM manipulation to the C++ the browsers are written in.

Using your framework (react/angular/etc) is leaving the part of the framework thats using innerHTML/createElement to leave the DOM manipulation to the C++ the browsers are written in.

Whichever path you take, the browser must do some DOM manipulation to render anything.. because that is what browsers are built to do.