4 ms·
I mean, they'll at least have the job until the project is finished. You're boss probably won't care if another framework comes out. Then there's all of the leg
by 6DM 10y ago
I mean, they'll at least have the job until the project is finished. You're boss probably won't care if another framework comes out. Then there's all of the legacy applications that will need support. There's an entire market for that. In the meantime you can learn something new :)
- at-fates-hands 10y ago>> There's an entire market for that. I can confirm this. I work in a large corporate environment and we're rebuilding a legacy application in Angular 1.4. They have no plans of migrating and even talk of moving to 1.5 or even 2.0 I've been told migrating to either 2-3 years away.
- wwweston 10y ago>> In the meantime you can learn something new :) The problem I've come to have with this as I get older is... I realize that I have a limited amount of time to learn new things. I still love doing it, but if possible, I'd rather spend that effort on learning portable, enduring, and broadly applicable things than ephemeral arcana involved in learning to do essentially the same thing a different/"modern" way. New learning should be for new capabilities, a better quality of insight, and real advantages.
- 6DM 10y agoOh yeah, I definitely get that. My main point is there's no reason to be outright afraid when a new framework arrives. I would argue there's even time to let it mature and see if it's actually worth learning.