4 ms·

It's not immediately obvious what this has to do with Inversion of Control. I didn't really know much about continuations, but from what I can gather it's not

It's not immediately obvious what this has to do with Inversion of Control. I didn't really know much about continuations, but from what I can gather it's not obvious they're a good idea (http://okmij.org/ftp/continuations/against-callcc.html http://okmij.org/ftp/continuations/against-callcc.html) - Ruby removed it's in-built support for it (https://bugs.ruby-lang.org/issues/10548 https://bugs.ruby-lang.org/issues/10548).

theoh 7y ago
The concept of continuations is well-established and they have their uses. They have been part of the landscape for years. They can be confusing, and that's impossible to separate from their power. The inversion of control that this paper is talking about is the way an application running on a webserver typically gets called by the browser rather than the other way around. Continuation-based webservers reverse this inversion and create an illusion of continuity of control flow on the server side. The application is suspended when a page is sent to the browser and resumed (via a continuation) when the response arrives. So this is about permitting server-side applications to be written in a nicer style as far as control flow is concerned. I think you are getting downvoted because your comment more or less says that you don't know much about the background, and haven't read and understood the paper, but are inclined to dismiss it anyway.
- arethuza 7y ago
  Doesn't HN run on Arc which can use continuations for handling some web stuff? https://arclanguage.github.io/ref/srv.html https://arclanguage.github.io/ref/srv.html NB I've never looked at the sources for HN
rhacker 7y ago
Same here. when I read/see IoC my immediate thought was Java/Spring. And yes, for the most part IoC as a concept is dying. More and more developers want to hold a function that returns hammers. They don't want a hammer factory factory factory anymore.
- theoh 7y ago
  The paper is literally about doing away with the inversion of control.

theoh 7y ago

The concept of continuations is well-established and they have their uses. They have been part of the landscape for years. They can be confusing, and that's impossible to separate from their power. The inversion of control that this paper is talking about is the way an application running on a webserver typically gets called by the browser rather than the other way around. Continuation-based webservers reverse this inversion and create an illusion of continuity of control flow on the server side. The application is suspended when a page is sent to the browser and resumed (via a continuation) when the response arrives. So this is about permitting server-side applications to be written in a nicer style as far as control flow is concerned. I think you are getting downvoted because your comment more or less says that you don't know much about the background, and haven't read and understood the paper, but are inclined to dismiss it anyway.

arethuza 7y ago
Doesn't HN run on Arc which can use continuations for handling some web stuff? https://arclanguage.github.io/ref/srv.html https://arclanguage.github.io/ref/srv.html NB I've never looked at the sources for HN

rhacker 7y ago

Same here. when I read/see IoC my immediate thought was Java/Spring. And yes, for the most part IoC as a concept is dying. More and more developers want to hold a function that returns hammers. They don't want a hammer factory factory factory anymore.

theoh 7y ago
The paper is literally about doing away with the inversion of control.