Yes that would be a good idea.
So I hope that we will be able to clean the stream part of Pharo.
But the problem is the users of streams. The stream API is too wide, people
expect hundreds of methods to be there, mixing characters and bytes, encodings,
line end conventions, infinite buffering, arbitrary positioning, and so on.
Many of these characteristics can be elegantly composed, just when you need
then.
Right now we have some cool streams in the image, with minimal APIs, targeted
at just one function. Like Guile's new file streams, the Zn streams, Zdc socket
streams, we just have to use them.
So what could be a plan?
Where should we spend energy?
Stef
