http://www.u.arizona.edu/~rubinson/copyright_violations/Go_T...
If you actually read the letter you can see that it also applies to modern programming and not just to "goto". Its truly a timeless article that everyone should read (and its really short!)
You could read it as a manifesto for solutions to callback hell which do not mess up your program's state, such as reactive programming.
http://www.reactivemanifesto.org/
http://www.u.arizona.edu/~rubinson/copyright_violations/Go_T...
If you actually read the letter you can see that it also applies to modern programming and not just to "goto". Its truly a timeless article that everyone should read (and its really short!)