Yeah, I'm very keen to constantly look at new packages / libraries / tech / etc. But it's extremely rare when I actually recommend that we adopt those shiny new things. I guess you can say I've become a tech window shopper. I can easily browse through dozens of new tech solutions without ever feeling the need to "buy" one of them and take it home.
For me, it always comes down to one simple question:
Which problem, that I'm experiencing in my current environment, does this new approach solve???
Soooo many times, when I look at new solutions, the answer to this question is just... crickets. Often, the "answer" is just that the new approach is somehow awesome and the old approach supposedly sucks - which I almost never agree with. Sometimes the problem solved by the new approach is something that doesn't even apply to our environment.
what third parties are contributing to this framework?
who is using this today? is it popular?
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..
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...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yeah, I'm very keen to constantly look at new packages / libraries / tech / etc. But it's extremely rare when I actually recommend that we adopt those shiny new things. I guess you can say I've become a tech window shopper. I can easily browse through dozens of new tech solutions without ever feeling the need to "buy" one of them and take it home.
For me, it always comes down to one simple question:
Soooo many times, when I look at new solutions, the answer to this question is just... crickets. Often, the "answer" is just that the new approach is somehow awesome and the old approach supposedly sucks - which I almost never agree with. Sometimes the problem solved by the new approach is something that doesn't even apply to our environment.
To me it always comes down to:
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..
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...