Consider not using #subStrings: in WAUrl>>addToPath:

[GoogleCodeExporter]

String >> #subStrings: in Pharo 1.1 has quite bad performance characteristics 
because it does a lot of allocation. In addition the semantics are quite 
overblown in our case because we only have a single separator.

In general I don't think you should optimize unless you have a performance 
problem but see the following tally from Issue 608

5.5% {1100ms} WAUrl>>addToPath:
  4.8% {960ms} ByteString(String)>>subStrings:
  1.6% {320ms} ByteString(SequenceableCollection)>>,
  1.0% {200ms} ByteString(SequenceableCollection)>>copyReplaceFrom:to:with:

Original issue reported on code.google.com by philippe...@gmail.com on 3 Nov 2010 at 8:29