I guess with respect to this specifically, I think the state should be stored explicitly by the application, not implicitly by the language or framework. In a continuation-based framework, state is captured in the form of the call stack, and stored transparently. Far too clever for me, and hides the developer from things the developer shouldn't and can't really be hidden from.
Isn't this just another example on varying level of abstaction in different systems? To pick couple of (hopefully) non-controversial examples:
- do you feel comfortable relying on operating system to store the state of your process?
- do you trust on language to handle memory management automatically for you?
Whether the abstraction fits into a particular task might also be just a matter of how well it fits into one's mental model of the problem :)# Tero Saarni
If the alternatively is manually coding in a spaghetti-ish continuation passing style-like way then give me continuations please.# Nico
If the alternative is manually coding in a spaghetti-ish continuation passing style-like way then give me continuations please.# Nico