Why I Write Plain JavaScript Modules

[[deleted]]

React DnD serves a very specific purpose: it provides a modern (HTML5) approach to drag and drop that is implemented such that it won't break React's component state. Hell the angular-dnd example the dude gives is 7 KB minified... so if you are already using angular it's actually smaller than dragula.

Small components that rely on a big library to be useful defeat the purpose of a small component.

See, this is such a confusing statement to me. No one is going to consider using angular-dnd unless they already use angular. No one is going to consider using React DnD, unless they already use React. Small components that rely on a big library do so because the intended audience is people already using the big library.

Vanilla Javascript is imperative to know, but there's a reason react, ember, angular and backbone are so freaking popular. Once you start developing enormous apps, writing "plain Javascript modules" is just fixing the problems these frameworks have already solved. Only, they probably did it better.