And of course we're interested in feedback and ideas on how to proceed with the situation.
A few comments I got at ESUG:
- do an ecosystem analysis to see what parts of the API are most used (and therefore sensitive to evolution)
- check the cost of String allocations; YBuffer was an effort in avoiding useless copying of string data
http://www.squeaksource.com/ajp--
Damien Pollet
type less, do more [ | ]
http://people.untyped.org/damien.pollet_______________________________________________
Esug-list mailing list
[hidden email]
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org