But doesn’t streaming have a place, like where data arrives in small independent blocks which, when taken together, can exceed system memory, and which, if processed as they come, are a more efficient use of CPU time, since we no longer block on I/O?
Basically, it was the wrong type of library/implementation for the job, in my reading.
The unescaping wasn’t being incrementally productive so it wasn’t working well here. There is a requirement that in order to benefit from a streaming ${THING} that you need to be able to express your problem in terms of piecework. Sometimes this is an unfamiliar reformulation of something we already know, sometimes it’s difficult but doable, sometimes we just don’t know how to do it in terms of streaming. I’m not sure where in that spectrum the unescaping fits into.
But doesn’t streaming have a place, like where data arrives in small independent blocks which, when taken together, can exceed system memory, and which, if processed as they come, are a more efficient use of CPU time, since we no longer block on I/O?
Basically, it was the wrong type of library/implementation for the job, in my reading.
The unescaping wasn’t being incrementally productive so it wasn’t working well here. There is a requirement that in order to benefit from a streaming ${THING} that you need to be able to express your problem in terms of piecework. Sometimes this is an unfamiliar reformulation of something we already know, sometimes it’s difficult but doable, sometimes we just don’t know how to do it in terms of streaming. I’m not sure where in that spectrum the unescaping fits into.