Mutability will literally prevent you from doing good work in the long run, unless you have a constant + consistent mitigation strategy. Good luck enforcing that discipline. You’re much better off starting with the right tool for the job.

I think this is a good point, as soon as you require developer discipline, you've lost

As deadlines, pressure etc affect the work, things like mutability, tests, quality etc will go out of the window

I was wondering if there were experienced Clojurists that had experience with Go, and specifically with the Reader and Writer interfaces. I find them pretty interesting and they seem to be especially well suited to streaming data. The thing I find unfortunate is that they deal exclusively with bytes. For instance, encoding something to JSON and streaming it into an HTTP request looks like this:

reader, writer := io.Pipe()
gzipWriter := gzip.NewWriter(writer)

go func() {
  json.NewEncoder(gzipWriter).Encode(myThing)
  gzipWriter.Close()
  writer.Close()
}()

req, _ := http.NewRequest("POST", someURL, reader)
client := http.Client{}
(req)
reader.Close()

@ruyvalle Sounds roughly like InputStream and OutputStream

looking at InputStream now, that does look very similar, thanks!