3 ms·
I spend a lot of time trying to contain state in event driven software with callbacks, it's a big hassle. My thought was that there are other cases where you a
by Gibbon1 8y ago
I spend a lot of time trying to contain state in event driven software with callbacks, it's a big hassle.
My thought was that there are other cases where you are really just doing batch processing blocks of data and then performing some action. And not holding state internally between runs. That's the usage case.
Thought was if you don't have neither mutable data and don't reuse stack frames. You can see exactly what happened if something goes wrong. And avoiding the heap means it's fast and deterministic.