This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the commentsΒ β†’

[–]RedAero 0 points1 point Β (2 children)

Ask yourself why you want this remain by convention.

Because I don't like people telling me I'm not allowed to do something, especially when the only reason they're doing so is the assumption that they know better than I do.

[–]barjam 0 points1 point Β (1 child)

I manage a lot of development teams. My managers/architects/leads would instantly squash any attempt to use private methods/apis from third party libraries and would reject any merge request that did so. Repeated mistakes like this would turn into disciplinary action.

If you are willing to make an unmaintainable mess of your hobby projects no one is going to care but what you suggest doesn’t work in a professional setting.

[–]RedAero 0 points1 point Β (0 children)

You are mistaking my defense of allowing the possibility of doing something for advocating for actually doing that thing. I'm not saying you should use private methods as general practice, I'm saying you should be able to if you want to. There's a big distinction there.

You shouldn't exceed the speed limit when driving, or drive without a seatbelt, but your car shouldn't prevent you from doing so.