5 ms·
To me, the issue isn't that modern JavaScript frameworks are sub-optimal, but rather that proficiency in the high number of competing frameworks is a sizeable t
by ZenoArrow 13y ago
To me, the issue isn't that modern JavaScript frameworks are sub-optimal, but rather that proficiency in the high number of competing frameworks is a sizeable time sink that shouldn't need to exist. These frameworks are essentially band-aids over the true issues in the core web development tools, and until that core matures to the point where the frameworks are unnecessary then you'll still see people reluctant in investing much time in absorbing knowledge that is likely to rapidly become obsolete.
- mzarate06 13y agoFully agree. I love JavaScript, but I hate having to switch between BackBone, Angular, Dojo, etc. between projects. Learning each one, as well intentioned as they are, winds up being a productivity hit at some point, if not semi-regularly. In a way I feel as if I've spent more time learning how to get things done w/JavaScript frameworks, than actually getting them done.
- sophacles 13y agoEven more frustrating than what you said (which is very frustrating) - Having already learned ember or backbone or whatever last year, I need to revisit it, or want to use it in my current project because it fits nicely. Or rather it used to. Turns out that in making it better (for whatever the "it" is) they changed fundamental bits on you, in such a way that you basically have to learn another new framework. Heaven forbid you go back and maintain the stuff written with the old version of the framework...
- mzarate06 13y agoYes, and that's why I'm now gun-shy to adopt any framework, JavaScript or otherwise. For example, in LAMP context, I hit the problem you mention w/the Zend Framework 1 -> Zend Framework 2 upgrade path, as well as with Kohana 2 -> Kohana 3. ZF 2, in particular, pushed a lot of loyal ZF devs away, and after trying to upgrade existing projects, and use it for new projects, I'd say rightfully so. Now I'm stuck maintaining a large handful of projects built on top of unsupported frameworks.
- r0s 13y agoAgreed. This also creates the problem of avoiding fundamentals. Is javascript really so bad we need to work exclusively in frameworks? Does CSS really need pre-processing? I think the answer is 'sometimes', but these days people treat these new layers of complexity as non-negotiable.