Churn Anxiety
Published ....
Last modified ....
Share this post on BlueskySee discussion on Bluesky
I recently ready this really good post titled Cold-blooded Software, and it got me thinking about the two primary reasons that I tend to avoid adopting new software:
- There's a semver major change coming soon
- The software has become abandoned
The second feels reasonable, why invest in something that is no longer maintained, no longer gets bug fixes or new features, or nowadays more importantly keeps up to date with the other libraries and frameworks that it gets adopted alongside. A recent example of this was that I wanted to look at adopting Contentlayer for my personal blog, however I checked a few open issues and noticed that the core maintainer of the library hasn’t been active for a number of months at the time.
My immediate reaction was that I didn’t want to adopt it because it might not keep up to date with other features or libraries that I used in my personal blog.
However, this isn't the point of the post, instead the first reason above I haven’t really seen much content be produced about, but it honestly keeps me away from libraries and frameworks far more often than the abandonware case, and it seems like it impacts others just the same: