3 ms·
The alternative to using private methods or reflectively mucking about with library/platform internals isn't always "do the same thing but with only public API"
by thfuran 1y ago
The alternative to using private methods or reflectively mucking about with library/platform internals isn't always "do the same thing but with only public API"; it's sometimes "you can't possibly fix the bug or implement the feature that you want to". It sure does increase maintenance burden though.
- bigstrat2003 1y ago> it's sometimes "you can't possibly fix the bug or implement the feature that you want to" Yes. It is, and that is what any responsible person should choose.
- thfuran 1y agoSo you'd tell customers "No, I'm not fixing that bug because doing so would offend my aesthetic sensibilities. Yes, I know you have a support contract, but I simply refuse to address your problem even though I could"? Or maybe you'd phrase it a little differently in public.
- rogerrogerr 1y ago“Poor decisions on your part do not constitute an emergency on mine.”
- willis936 1y ago"Poor decisions on a third party's part do constitute an emergency on mine."
- frumplestlatz 1y agoYes, I have told customers exactly that when there was no supported way to achieve what they wanted. I'm not putting my name on that.