Re: Re[4]: additional methods in NSMutableString

[Adrian Robert]

> > o will it be possible to add a method in NSMutableString like this: 
> > -setCharacters length: ...
>
> Just to add a more general comment ...
>
> One of the big advantages of OpenStep / Cocoa is it's simple, easy to 
> remember API.
>
> Adding methods also has disadvantages:
...
> - Writing applications becomes more difficult since you have to 
> choose from a 
> bigger set of methods.

If you want to see how an API ends up when semi-specialized methods 
are added to optimize for many situations, look at Java, particularly 
1.4 or even worse, 1.5.  The library contains several times the number 
of classes and methods to accomplish much the same functionality as 
OpenStep, and places an unnecessarily large cognitive load on 
developers.  The costs of this should not be underestimated -- mental 
resources are finite.  This problem in Java has resulted from other 
factors besides micro-optimization, including the non-removal of 
deprecated methods and classes, but nonetheless serves as a good 
example of what NOT to do in maintaining an API.

I don't know about the specific issue of path methods for 
NSMutableString, but it might bear some thinking why NeXT/Apple has 
never seen it necessary to have these methods.