4 ms·
> I've used Angular 2/4, React, and Vue. I like them all, and I'd be happy to work on a project using any of them. Aurelia looks equally enjoyable. I've used A
by atom-morgan 9y ago
> I've used Angular 2/4, React, and Vue. I like them all, and I'd be happy to work on a project using any of them. Aurelia looks equally enjoyable.
I've used AngularJS, Angular2/4, and a bit of Backbone and Ember. I agree about React, Vue, and Aurelia and despite what hiring managers may think, I don't see competent engineers having much of an issue switching from one to the others.
- rpeden 9y agoI agree, and expanded on it in my reply to Analemma_. Hiring has become too framework specific - if someone has built an application using a component oriented framework, I don't think they'd have much trouble moving between them. I'd even cast a wider net when looking for good candidates while hiring - if I came across a great developer who knew JavaScript well and had also worked on WPF apps in the past...I'd probably be inclined to make them an offer, even if they hadn't worked with React or Angular yet. Maybe it's like Moneyball applied to the developer labor market. There are lots of people who would do a great job, but are undervalued because most hiring is fairly buzzword-oriented at most companies. Frameworks and tools come and go. I think that the real value comes in understanding the underlying concepts and being able to apply them in new situations using new tools.
- emodendroket 9y agoI'm currently working at a place that is basically tech agnostic when it comes to getting and it's pretty good in my experience.
- noir_lord 9y ago> I don't see competent engineers having much of an issue switching from one to the others. I went from been a "dyed in the wool" desktop/enterprise developer to a backend web developer in less than a year and a full stack in two, once you accept the patterns are different, programming is mostly just programming. Here we are in 2017 and if you squint web app development looks a lot more similar to that stuff than it did back in 2009, I picked a fairly good time to move over I think, I missed a lot of the early bullshit around browser incompatibilities (I just caught the tailend of the shitfest that was older IE versions) and the tooling has improved hugely over that time. TypeScript with node and some of the front end tooling is actually pretty pleasant day to day.