Re:Observing the second law of thermodynamics in software
by kbenson on Tuesday May 29, 2018 @01:57PM
(#17181476)
The ability to quickly use your PR for a system that was overly private is beneficial, but is still decidedly non-zero in terms of time and effort. The PR has to be written in the first place, for example. And that's before we get into whether upstream even accepts your patch without modifications, or even accepts it at all.
[ Parent
| on HN ]
Re:Observing the second law of thermodynamics in software
by dustingetz on Tuesday May 29, 2018 @01:59PM
(#17181496)
he means we can fork and vendor locally but it doesn’t scale when doing enterprise java for many reasons
Re:Observing the second law of thermodynamics in software
by wereHamster on Tuesday May 29, 2018 @03:37PM
(#17182298)
I'm always assuming that upstream will either accept the PR, or explain how to achieve my goal without requiring a change to upstream. Either way, such a pull request should be resolved fairly quickly and not linger around for too long.
Why does this not not scale when doing enterprise java? Is it the 'enterprise', or 'java', or the combination thereof?
Re:Observing the second law of thermodynamics in software
by dustingetz on Tuesday May 29, 2018 @09:07PM
(#17184154)
Many reasons, cultural, not often on github or developed openly, huge variance in quality, maybe not so agile, huge code drops every 6 months with tons of churn so even tiny patches can add huge overhead to the rebase when you upgrade versions soooo you don't.