With full respect for your choices, I don't have your code in front of me so I can't review or comment on architectural decisions made, but given that disclaime

With full respect for your choices, I don't have your code in front of me so I can't review or comment on architectural decisions made, but given that disclaimer - when people say they "need" a plugin to do something, I often wonder if their viewpoint is accurate to the real problem being addressed, or if they are programming by habit, rather than by best practice. Again, I mean no disrespect because I have no information to criticize other than base assumptions. To Excel, I wonder how much reimplementing was needed again, did you need computations in-cells like Excel has? It seems like if you are going that deep you will need to implement much of the logic on your own. I guess if you are truly just reimplementing Excel in a web interface, then your point has merit, but it seems like for something that specific, the preboxed solution would more get in the way? To directives versus components, certain behaviors make more sense to me as an HTML element (an infinite scroller, for example) than as a "controller-level" component. Additionally I've found a great transparency of debugging by starting with the HTML and looking at what functions are being invoked when, than by hoping I know where the "controller" is binding into the HTML, and perhaps never finding all of it. And fair - I still don't know what "opinionated" means... lol