I do agree we have become used to productive toolkits like jquery.. demands for developer productivity don't change because of the tool chain.
Interesting perspective..I chose angular because of the restrictive design architecture which can serve to improve quality and ease into automated testability once the methodology is understood.. The use of directives as adapters to other tool chains inherits the quality practice of the dependency, somewhat defeating the benefit of angular while incurring the additional overhead.
I don't think the communities will ever make up their minds on the "next" javascript tooling.. Syntactic candies will entice each graduating class with a new shiny toy in each box.. Not everyone will like the same flavors.
The dnd and selectable are all specific cases of the more generalized editing functions (insert,cut,paste,delete,select,deselect,undo,redo) which are not fully formalized in the current angular framework and has implications to drawing, charting and other diagramming widgets and tool chains.
The browser has the capability to cut/paste from the OS. The data format is an issue.. There are monolithic solutions supporting some of those capabilities, eg. ckeditor, but they lack modularity impedance to align with the angular way.. Today, moving to angular is reminiscent of programming in C/C++ moving to a mature java tool chain, then moving back to C.. It is painful, and I hope its worth the investment.
As for my little project, I'm looking at the jqueryUI directives to get a viable multilist, sortable working in a jquery layout. I'm dragging icons from sortables across different viewports to a sortable target which converts the icons to portals on drop. Very painful to attempt in angular right now.. I'll have to attempt something similar into a ckeditor target as well.
Unfortunately, there are few examples in this space..