11 ms·
This is just one of the reasons why I feel developing web apps has gotten harder. While there are a lot of javascript frameworks it is likely two projects pick
by jtchang 13y ago
This is just one of the reasons why I feel developing web apps has gotten harder. While there are a lot of javascript frameworks it is likely two projects pick different routes. It basically means if I need to maintain a project I will have to learn a new javascript library.
- nilliams 13y agoHmm, I see why it could feel like that but I don't really agree. Here's another angle: Would you rather learn some (hopefully) very well worked-out library with good documentation and all the edge-cases slaved over, with multiple contributors, with Stack Overflow questions about it ... or, would you like to learn some random guy's non-library library, because he was scared of libraries, so he just made up a load of ad-hoc conventions in his codebase. I'd rather learn to use Backbone, Angular and Ember, than have to deal with big-ball of mud code based on no library in particular. Same goes for templating libraries, I'd rather learn a handful (after all they're relatively trivial to use), than come to a codebase that uses none at all.
- bjhoops1 13y agoAlso, if you're using a tool that was built more than a year ago, you risk ridicule. Definitely a lot more work figuring out what the hottest new tools are than in traditional or backend development.
- jfarmer 13y agoIt's the ciiiiircle of life. We're at the "Cambrian Explosion" stage of front-end frameworks. The variance in approaches, technologies, and boundaries between the various moving parts is just the ecosystem sorting itself out. Come back in 3 years. It'll have settled down.