Doing anything halfway complicated with React, such as implementing browser fingerprinting, means building a complex stack of components that you then have to c

Doing anything halfway complicated with React, such as implementing browser fingerprinting, means building a complex stack of components that you then have to constantly maintain and manage. The alternative to building a complex stack of components in your framework is to build the thing you want in vanilla JS (exactly as you would with plain ES6) and then call it using a hook. The maintenance overhead for complicated things that don't integrate in to the framework well will be exactly the same, but you also get to use the framework for things that do integrate well. So no, ES6 isn't going to replace anything. It will augment framework use in some edge cases with high complexity. That's exactly how things work now. The problem with the article is that the author thinks overcoming the difficulty in building a complex application is a matter of writing better code. That is wrong. The way to build a complex application is to be more organised. That's what frameworks make easier, even if the code ends up being pretty horrible.