> Vanilla JS? Yea, no thanks. I'm not going back to square one, choose your own adventure custom framework because of your skill issue.
Isn't it the other way around? Those who have skill issues select React?
Isn't it the other way around? Those who have skill issues select React?
It's possible to write a whole load of very clever things in vanilla JS, but it's not always a good use of time to do so, and it is not a very easy way to develop things in large teams, without building up an abstraction layer with getters and setters that is not appreciably better than a minimal reactive framework.
The one-way data flow in reactive frameworks is the bit worth fighting for (and fighting over).