News for hackers. Stuff that matters.
Re:Why scaling and parallelism remain hard even with new too... by pyotrgalois on Wednesday August 10, 2016 @04:33PM (#12264575)
In some way this article by one of Erlang creators is related to your comment: https://armstrongonsoftware.blogspot.com.ar/2008/05/road-we-...

> The fundamental problem with taking a remote operation and wrapping it up so that it looks like a local operation is that the failure modes of local and remote operations are completely different.

Re:Why scaling and parallelism remain hard even with new too... by derefr on Wednesday August 10, 2016 @07:52PM (#12265488)
I think of Erlang less as making remote operations masquerade as local ones, and more as forcing you to assume that all local code has the potential failure-modes of remote code. Which, often (for weird and roundabout reasons) it does.
Re:Why scaling and parallelism remain hard even with new too... by im_down_w_otp on Thursday August 11, 2016 @02:54AM (#12266645)
This.
Re:Why scaling and parallelism remain hard even with new too... by jeffdavis on Thursday August 11, 2016 @01:38AM (#12266447)
Very insightful!
Re:Why scaling and parallelism remain hard even with new too... by qznc on Wednesday August 10, 2016 @05:23PM (#12264846)
Armstrong clearly sees the problem. I understand his solution as: Erlang makes local and remote actors indistinguishable, but you should build your own custom wrapper for remote calls.

This seems fishy to me. You build low-level boilerplate over a high-level foundation? To clarify, I consider implementing the timeout as "low-level" and a mechanism like "link(remote_process)" as "high-level".

Re:Why scaling and parallelism remain hard even with new too... by pyotrgalois on Thursday August 11, 2016 @10:29AM (#12268492)
Could you please explain why do you think a timeout would be low level?