4 ms·
When I saw the link title, my first thought was "why do we need yet another new MVC Javascript framework"?
by superqd 13y ago
When I saw the link title, my first thought was "why do we need yet another new MVC Javascript framework"?
- tomelders 13y agoThat's sort of like the tone Microsoft took after releasing ie6. Landscapes change. Every single js framework in existence today will be unfit for purpose in 10 years. So we enhance the frameworks we have and try out new ones so in 10 years time we don't find ourselves stuck with tools that don't work anymore.
- Zelphyr 13y agoThe problem is the shear volume of new frameworks. Writing your own framework has almost become a rite of passage for software developers. And I'm not knocking that. I did it myself. I learned a lot, the most important of which was that my framework was crap and that I didn't really need it at all.