Re: Nim's strutils.split() slower than Python's string split()?

[cblake]

Locking can indeed slowdown output as can exception handling and is unnecessary 
for single-threaded output and the exceptions may be unhelpful if there is 
nothing you can do on out of space errors. If you are on Linux/glibc then you 
can also just use `fwrite_unlocked` directly as in `cligen/osUt.nim:urite` or 
`cligen/mslice.nim:urite` as shown in the `examples/cols.nim` program in 
[https://github.com/c-blake/cligen](https://github.com/c-blake/cligen)