If the goal of "micro JS" truly is file size then yes, that's focusing on the wrong problem. To me the idea behind it is to have a bunch of little tools that d

If the goal of "micro JS" truly is file size then yes, that's focusing on the wrong problem. To me the idea behind it is to have a bunch of little tools that do one thing really well. When those tools are combined you have something very powerful, flexible, testable, and reasonably decoupled. Not perfect. Nothing ever is. But better than having to use a massive framework and do everything the framework way in which case you're just working for the framework rather than it working for you. In my experience that is ALWAYS the case with a framework. Put another way, Unix has been so popular for so long in part because it prefers the "a set of tools that do only one thing but do it really well" philosophy over a framework.