JavaScript frameworks exist as a tool for developers to abstract away some of the more complex aspects of developing front-end applications. So before you get defensive about your favorite framework, let me explain why I think this shift will occur. In other words, JavaScript frameworks will die in the same way, and for the same reasons, that Flash died-because there was simply no need for it anymore and the inherent security vulnerabilities made it dangerous to use. Rather, I think two of the key features of ES6 (modules and classes, specifically) will make many of the most popular frameworks obsolete. I’m not saying that JavaScript will see its use narrow-in fact, plenty of companies are hiring JavaScript developers right now. I know that’s going to be an unpopular conclusion, but hear me out.
The JavaScript developers of the future won’t use frameworks. However, I want to argue for a more radical prediction: As developers get more and more familiar with what ES6 can do, we will finally break this cycle.
Frameworks aren’t nearly as popular as they were when ES6 first came out, while JavaScript is going strong. With ES6-arguably the biggest change to the language yet-the same cycle could repeat again. Then, in the relatively long periods between releases, frameworks begin to offer new features and tempt developers back. They move back to coding directly in JavaScript, and frameworks become less popular. At first, developers are delighted by the new features. Every time JavaScript goes through a major update, we seem to repeat the same cycle.
0 kommentar(er)
