DEV Community

Discussion on: Why Older People Struggle In Programming Jobs

Collapse
 
aminmansuri profile image
hidden_dude

To me it always comes down to:

  1. what third parties are contributing to this framework?
  2. who is using this today? is it popular?
  3. out of those options which is least horrible

Sadly these are important considerations, because if it's losing popularity then soon it will have no support and then it will become costly.

But none of these considerations are technical considerations. It's mostly a popularity contest. We don't have the luxury of using the best tech that is no longer supported or soon to die.

Though some considerations could also be load time, how heavy the library is, etc..

Thread Thread
 
bytebodger profile image
Adam Nathaniel Davis

Oh, I totally agree. And at the risk of being semantic, I will say that my original question (about which problem it's solving) could, in fact, be the "problem" of support / popularity / etc. Those are not illegitimate considerations. But even under those scenarios, I'd have to be convinced that our Current Established Tech is truly going the way of the dodo bird before I'd wistfully embraced Hot New Tech. It wasn't that long ago that people were convinced that they had to embrace Ruby on Rails to address the "problems" of support / popularity / etc. And we saw how that played out...