3 ms·
You're absolutely right that it's neither fair nor productive to dismiss any crituque out of hand. I just found this article to be on dogmatic side of the spec
by rpeden 9y ago
You're absolutely right that it's neither fair nor productive to dismiss any crituque out of hand.
I just found this article to be on dogmatic side of the spectrum. It doesn't seem that the author has enough experience with Angular to back up the negative assertions made about it.
I know it's only anecdotal, but I've seen teams that are simultaneously using both Angular and React happily and productively. When I've talked to people working on those teams, they don't really feel that one is drastically better or more fun to use, and they've found that speed of development and codebase maintainability ar comparable between the two.
- hashkb 9y agoWe also have this idea now that spending an afternoon with some tech is enough experience to share with others. Initial learning curve and "am I immediately as productive as I wish I was?" have somehow become key metrics.
- unclebucknasty 9y agoTrue. It cuts both ways though (I guess like most things). That is, once a person has invested in that learning curve and spent significant time working in a tech, tunnel vision tends to set in. It becomes the only tool, which that person fiercely defends. They've now got too much invested to just let it go. It's actually not unreasonable from a raw self-preservation/self-interest perspective, but I do think it contributes to a lot of the emotion-filled tribalism we see. In other words, the intensity comes as much from interest in maintaining self-relevance and personal financial security as from the viability of the actual tech.
- unclebucknasty 9y ago>I've seen teams that are simultaneously using both Angular and React happily and productively Yeah, it really is just a matter of opinion and thinking styles. I'm not sure why we're so bent on this idea that we should all do everything the same way. Part of it is self-preservation, I suppose. "I've got 20 years in Java and you're telling me it sucks (and, by extension I suck too)? You and I now have a problem." But, we keep doing this with any new tech, and never seem to get that it'll all change and matters a lot less than we think. What people raved about 5 or even 3 years ago is now passe'. Call it evolution, and that's probably a good thing. But seems we could have learned to skip the part where we beat each other over the head while awaiting The Next Big Thing. Funny thing is that no matter which framework you like, the worst thing you can do is not choose any framework. People can't even wrap their heads around the fact that you haven't declared a side.