When writing a framework, I always ask myself what is this doing that cannot easily be done with the native APIs?. Answering this question is easy for both Ang

When writing a framework, I always ask myself what is this doing that cannot easily be done with the native APIs?. Answering this question is easy for both Angular and React: in both cases they enforce conventions that make certain flavours of software development easier. What advantage does Zam have over using the regular DOM api? AFAICT, Zam doesn't introduce significant changes to the underlying paradigms so by Occham's Razor I have a hard time believing this additional framework will help me. On a side note, I'm not sure why everyone attacks React and Angular so much. Believe it or not, they work very well for their intended purpose. There will always be hacks in every community who chose bazookas to catch butterflies but it's a fallacy to attribute that to the framework itself. Both React and Angular, IMO, enforce concerns that scale super-linearly w.r.t. to project size: e.g. mutating a DOM element is fine if you're the only actor on the document but definitely doesn't work when n actors all depend on the same DOM node to broker a shared state.