>When you have an unexplained performance problem, your response shouldn't be to "upgrade every single framework and plugin" that you use. Yeah. That jumped ou

>When you have an unexplained performance problem, your response shouldn't be to "upgrade every single framework and plugin" that you use. Yeah. That jumped out at me as well. They spent an inordinate amount of effort to solve a non-problem. It's great to stay on evergreen with versions, but probably not a good thing to do so while you're desperately trying to debug a problem. I suspect this was a hopeful but lazy attempt - in the spirit of "Maybe if we just do this, it will somehow fix the underlying problem". It's a lazy approach to solving problems. Debugging performance bottlenecks is hard and devs generally hate doing it. Upgrading version dependencies is a known factor and developers are comfortable with that.