For quite a while I’ve had a React vs Bindinator comparison on the bindinator site. It compares the way the screen redraws in React’s simple To Do example (it’s the bottom example on the reactjs.org home page) vs the equivalent Bindinator example. The results are not favorable to React. But hey, the React code is more than twice as long, and kludgier.
The resulting comparison is visual and makes its point immediatelyâ€¦
I tried to do a similar thing for Angular vs Bindinator but couldn’t find a similar tutorial. (The official Angular tutorial is way more complicated and didn’t have a live demo when I looked; it still doesn’t seem to have one.) So, I ended up going pretty deep into the weeds on fairly complex issues with Angular that is certainly not as simple as just showing horribly inefficient screen redraws.
But, tonight as I was thinking about Angular for another reason, I found this tutorial on Sitepoint. Now, the tutorial implements an Angular “service” for the To Do, and also implements some tests. All in all, it’s horrifically more complex than either the React or bindinator tutorials. Almost hilariously, the tutorial requires you to use Angular-CLI, a tool to generate scaffolding because boilerplate.
And it has a live demo.
If a picture is worth a thousand words, how much is this gif worth?
So, my basic point is that you can accomplish a task using bindinator with fewer lines of code, that are easier to read and understand, that runs more efficiently, than other leading frameworks.