5 ms·
Yes, if you learned React you'd have a decent shelf life still. What if you learned classic AngularJS, due to go unsupported in a month and a half? What if you
by NateEag 5y ago
Yes, if you learned React you'd have a decent shelf life still.
What if you learned classic AngularJS, due to go unsupported in a month and a half? What if you threw in with ExtJS ages ago and the enterprise corp you've been using it for just downsized and outsourced your project? Maybe you were an EmberJS aficionado but can't find new gigs using it. I worked on a greenfield project in Backbone/Thorax/Mustache a number of years back but haven't seen any of those in the wild since. Maybe you love Elm but can't find any places that will hire you to use it. Ditto using Clojure on the frontend.
Picking the winner is a great trick, but my point was that if you didn't (or just the companies you worked for didn't), you may find yourself in a bit of a hole, specifically if you have a lot of other responsibilities in your life.
- schwartzworld 5y agoSkills transfer across frameworks and even languages. If you're good at Elm or Clojure, you would be great at React. Vue owes a lot of its structure to the original Angular (or at least it did when I learned it forever ago).
- NateEag 5y agoSure, skills do apply across frameworks and languages. The hundred stupid things you need to know about any given framework don't, though. To be clear, I'm not thinking about people who've used lots of languages and tools here. I've done time working for huge corporations for whom software is a cost center, and it's easy to find people in those contexts who are competent with the tools they know but have narrow enough experience that moving to something else is difficult for them. The "average Joe" programmer's experience is what I'm thinking of here.