3 ms·
You'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 co
by mattmanser 10y ago
You'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.