The hosts discuss when to drop a tool, agreeing that the tipping point usually comes from external factors like hiring and integration support rather than the tool itself failing. ✦ AI generated
Wes Bos · Syntax · 2026-08-19 · original ↗
starts at this moment · 34:18
“When do you actually drop a tool that still works and is still maintained? My question is where the pressure really comes from.”
My question is where the pressure really comes from. Is it the tool itself getting worse or is it everything around it? Hiring libraries drying up, CI integration, the can someone else pick this up in 2 years problem?... there is a sweet spot in between hanging on to the good old trusty faithful thing that works well... and then it starts to creek, starts to get older, and you start to say, 'I can't hire for it.'
verbatim transcript · starts at 34:18
34:18getting worse or is it everything around it? Hiring libraries drying up, CI integration, the can someone else pick this up in 2 years problem? Has this there been a specific moment where you realize something perfectly functional has quietly become too expensive to keep? And as a bonus question, he says, "Any migration you regretted? Um, what did you think you'd gained versus what you actually got?" Yes, this is really
34:45interesting question because there is a sweet spot in between hanging on to the good old trusty faithful thing that works well, is well supported, has has been doing you well, and then it starts to creek, starts to get older, and you start to say, "I can't hire for it. a lot of the examples don't work as well as as they thought. Um, a lot of the new
35:08libraries that that come out are integrated. Perfect example I've had in this one is is Express. You know, I hung on to Express >> for probably 3 or 4 years longer than than most people did. And I finally got to a point where >> the TypeScript story for it sucked. Um, the integration of everything modern sucked. A lot of the new stuff that I wanted to use were not based on like the