Re:How we spent $30k in Firebase in less than 72 hours
by TeMPOraL on Thursday August 02, 2018 @01:34AM
(#17669414)
> If you do go and track down the problem in your depedency
This is the part the parent's cow-orkers didn't perform. There's nothing wrong in updating a dependency to include the fix for the problem you're experiencing. But the people in question were apparently too lazy/clueless to even track down the problem, opting for randomly upgrading stuff instead.
Re:How we spent $30k in Firebase in less than 72 hours
by macspoofing on Thursday August 02, 2018 @09:20AM
(#17671170)
>If you do go and track down the problem in your depedency and file a bug
There's a difference between upgrading your dependencies because you traced a problem that you know is fixed in the newer version and upgrading your dependencies because you hope it fixes a problem you don't understand.
Re:How we spent $30k in Firebase in less than 72 hours
by zaphirplane on Thursday August 02, 2018 @03:59AM
(#17669912)
There is a possibility you found a bug and a workaround is known/suggested
There is the possibility you are told you made a mistake in thinking it’s a bug with the library
If you do go and track down the problem in your depedency and file a bug, one of two things is likely to happen: they close it and say it's fixed in the latest version or they refuse to accept your bug because it's filed against an old version.
Skipping the track it down part and just jumping into upgrading can be a time saver. It works fairly well if you fit into the 'common' part of the user base with frequent updates. (Incidentally dependencies with frequent updates are kind of a pain)