3 ms·
I apologize in advance, but I, an ES5 / lean modules / no-build / vanilla javascript guy, find this article to be terrible advice. The arguments against framewo
by ricardobeat 10y ago
I apologize in advance, but I, an ES5 / lean modules / no-build / vanilla javascript guy, find this article to be terrible advice. The arguments against frameworks are backed by generalizations like
frameworks tend to intermingle display and business logic
testing is tedious and difficult
cycle time bs
I once used a framework... and had to wait months
Then goes on to say When we use a sound architecture and libraries instead - well, guess what? Frameworks are just architecture + libraries! In fact, your plan to release an "npm module" with architecture, diagrams and library dependencies is a framework, a mishmash of solutions of varying quality!
Of course they have varying levels of coupling - it's probably hard to replace parts of Angular, but Mercury for example is just a bundle of easily swappable libraries, like many others. React itself is not a framework.
It also completely overlooks the architectural differences that have come to exist in modern SPAs. What he proposes in the linked slides is just MV*, which everyone already has done for a decade. Flux-style state management + reactive rendering is a huge improvement over that and you won't get that just by using jQuery.
The author actually maintains a virtual-css library (PowerCSS) which benefits from the same principles, yet fails to see the value of doing the same with the DOM. This library + jQuery is already as large as many frameworks.
- mattmanser 10y agoYou're cherry picking. One of his key points is that frameworks aren't "just architecture + libraries". Read his 2nd point, "Frameworks and the inversion of control". Also, MV* hasn't been done in javascript for a decade. jQuery itself only came out a decade ago, MV* frameworks started appearing 5 or 6 years ago. 10 years ago most browsers in the wild were still IE6 which could barely handle 100 element for loops, let alone an mvc framework.
- zdragnar 10y agoThere are certainly JS MV* frameworks older than 5 years... Dojo and puremvc come to mind.
- dismantlethesun 10y ago> 10 years ago most browsers in the wild were still IE6 which could barely handle 100 element for loops, let alone an mvc framework. Heh, I should tell you a story about 'enterprise' level frameworks of the 2005 era, and the abomination of entangling them with ActiveX. Somehow, no one cared how slow a page was running, so long as it did it's job.