flat-zoo-3195210/14/2022, 5:54 PM
wide-midnight-7859810/14/2022, 6:15 PM
flat-zoo-3195210/14/2022, 6:25 PM
wide-midnight-7859810/14/2022, 6:30 PM
flat-zoo-3195210/14/2022, 6:31 PM
a lot... it's interface kinda sucks sometimes and is inconsistent from command to command, but I never really worry about it not working, unless I stumble onto some ancient version
wide-midnight-7859810/14/2022, 6:58 PM
was only a couple years old in its current incarnation, with a user base that was 100-1000x smaller?
I think it would be in a situation where consistency and cleanliness can have a higher priority over ultimate stability
It's a wobbly see-saw type of problem. I look at Bazel as a decent case study, where I think the API is pretty stable nowadays, but half the time, it's incomprehensible to me.
Well, that's a lot of grief solved.
The CLI is trickier though, admittedly.
I say all of this as someone who uses pants in about 25 repos with 10 clients so far - so anything breaking will require some pain and suffering, but I've also gone through LOTS of major breaking upgrades of languages and frameworks.
More often than not, the fear of it is worse than the action - and, other than XCode/Swift, I've chosen if/when I'm upgrading.
This also puts me on the side of the discussion which accepts breaking changes as a fact of life with open source software, so long as it's on my terms.
./pants migrate ::
bitter-ability-3219010/14/2022, 8:02 PM
busy-vase-3920210/14/2022, 8:02 PM
bitter-ability-3219010/14/2022, 8:14 PM
happy-kitchen-8948210/14/2022, 8:44 PM
witty-crayon-2278610/14/2022, 9:18 PM
bitter-ability-3219010/14/2022, 10:37 PM
flat-zoo-3195210/15/2022, 12:14 AM
bitter-ability-3219010/15/2022, 12:16 AM
busy-vase-3920210/15/2022, 1:05 AM