3 ms·
> I would assume that a competent web developer should be capable of quickly learning a framework Well, not that I disagree with you that a lot of employers ar
by commandlinefan 9y ago
> I would assume that a competent web developer should be capable of quickly learning a framework
Well, not that I disagree with you that a lot of employers are being awfully ridiculous when it comes to Angular background requirements, but... you're in for a shock if you try to pick up Angular quickly. Angular is more than a framework - or rather, Angular is a framework that depends on a sprawling ecosystem of other dependencies, each with its own idiosyncrasies. It's not just that Angular is a huge, complex, vast, partly undocumented framework that changes almost completely every few months (Angular 1 and Angular 2 are completely incompatible), but Angular is also heavily dependent on node.js and npm which are themselves pretty complex and prone to break in odd ways that Googling error message doesn't normally help much with. And that's assuming that you don't want to do any sort of unit testing, because the Karma/Jasmine/Protractor frameworks are themselves prone to unexpected breakage and version incompatibilities. But you'd better plan on doing a lot of unit testing, because debugger support is nonexistent too. This is all assuming you have a VERY good handle on HTML, CSS, and Javascript - don't even dream about trying to make sense out of Angular if you're not already an expert on all of those (especially Javascript, even though Angular doesn't use Javascript directly any more). I've been coding now for 25 years, and the only things I've seen come along that were as loved by executives and as fragmented and hard to troubleshoot have been Corba, EJB and Ruby on Rails... so I'm inclined to wonder if any time spent learning Angular will actually be well spent in the long term.
- expertentipp 9y agoThat's true, especially the testing part (ever seen chain of promises, a deferred object, and completely useless error stack trace?). Debugging? Source maps, transpilers, file watchers - impenetrable pulp. Why the community is so fixated on forcing the framework down the throat of developers? It certainly solves some problems, but these problems could probably be solved in a more comprehensible and simpler way. Angular it not the new cool thing - it's a complex thing with multiple versions, each incompatible with the others.