cool! Reviewing String is a chance to provide a clean, brief, readable API for what’s probably the most popular set of needs.
If you’re starting with computing it wont take too long to try to modify strings and get value from it. So doing more with the tool (instead of abandoning it for an easier alternative) is more likely. If you’re a veteran engineer you will face that too and end up appreciating the convenience. If you can do that in intuitive english instead of cryptic-memory-addicted things like printlf, etc then it’s an all win. Also wanted to say that you probably developed your most successful strategy but there is no single path or way to explore a system. Nature loves to try everything, all the paths, and select the most universally convenient. The more bridges we build the better* So, if the API additions are intuitive, then I’m all for it sebastian o/ *because, among other things, we would make possible the success of less myopic software models / views of the world / future innovations On Feb 25, 2014, at 3:48 AM, Pharo4Stef <[email protected]> wrote: > this is exactly the point of the project. > Rethinking the API. > And writing a systematic analysis of the situation so that we can get an > overview. > > Stef
