News for hackers. Stuff that matters.
Re:Java 24 by MarkMarine on Tuesday March 18, 2025 @04:45PM (#43404869)
you should have read the rest of it then, because in the context of Dijkstra's famous paper [0] (that this is written in the style of) the argument here is being able to understand program flow in the programmers' mind. Your description of the go func actually makes it WORSE, because the program doesn't just go there, it goes there later.

[0] https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...

Re:Java 24 by yubblegum on Tuesday March 18, 2025 @04:49PM (#43404903)
That may be true, but regardless, it is most definitely nothing like a goto and it is misleading. & Yes I have read Dijkstra and as it happens have my own critical views regarding Go's goroutines (which are really inspired by CSP), but just don't appreciate misleading assertions. To wit, "flow" does not really make sense in context of concurrency. Flows, plural, sure ..
Re:Java 24 by MarkMarine on Tuesday March 18, 2025 @09:38PM (#43407459)
Well fair, but I do think you should give this article a read. It’s the genesis of kotlin’s coroutines, and other implementations of “structured concurrency” or nurseries as the author conceives of them.