Until there are numbers, as in qualified by data, its all irrational. It doesn't matter that something costs money. What's important is how much more it costs (the difference).
People don't add more dependencies into ther code out of fear that's just a weird idea.
I'm not saying I know the cost, I'm just rebutting the comment about this being driven by fear. It's not, this is cost saving, and might be lousy at that, or not data driven.
By the way there is no such thing as "data driven software methodology", no one has ever done such a thing, so asking for it is just rhetorical.
I think that's the reason why a certain 3rd package is chosen.
the decision between roll your own and 3rd package often comes down to whether you want to sidetrack engineering _right now_ to write code that's not your product's functionality.
> A/B testing
you're talking about data driven product decisions. What we are talking about is data driven engineering decisions. Show me one article on such experiment?
the first problem is that there is no data. Last I checked developers are not fond of telemetry in their dev tools.
my point is not that's it isn't desirable. It's just not a thing that exists to bring up in arguments.
there is a difference between emotions (fear) and heuristics (this will cost time and is potentially buggy). I mean they are actually same in nature but at different points on the spectrum.
Fear of writing original code. There is less perceived risk (actual risk is slightly increased) if you can defer blame.