Tony Culshaw wrote:

I've considered using in in the past for a project and then rejected it as
being in the "api too unstable" basket.

Anything that ensures code that I cut now won't break later and has more of
a future gets my vote.

[+1] small to big.

[-1] big to small.



I agree.



Reply via email to