Not even. The point is you don’t need a “virtual DOM” to begin with. You have THE DOM. DOM binding is wizbang cool, but it’s more often than not overkill. If I need to monitor parts of the DOM for changes or change it on the fly, I can do that without a boatload of bloat which all of these frameworks essentially introduce.

Rich controls should be self-monitoring anyway and it doesn’t take a whole bloated framework to do that. It’s also very easy to organize reusable templates in the UI, again, I don’t need a framework to do that.

The bottom line is I can do all of the things you mentioned above WITHOUT a framework bloating my code or introducing yet another compile sequence and yet another something to breakdown in the CICD pipeline. So, in that regard, okay, I guess I’m a genius. LOL!

It’s just plain vanilla JS, or jQuery shortcuts. If you write clean, commented code, you don’t need documentation to figure out what’s going on within the DOM.