3 ms·
1. Old solution becomes new again 2. Folks clamor that we actually had things right the first time 3. Hype dies down 4. Blog posts complain that the solution
by ravenstine 3y ago
1. Old solution becomes new again
2. Folks clamor that we actually had things right the first time
3. Hype dies down
4. Blog posts complain that the solution "just doesn't scale" and that the complete opposite approach (or some hybrid) is better
5. GOTO 1
- mettamage 3y agoGOTO 1. Old solution becomes new again Points 2 and 3 4. Dijkstra enters the picture with the paper: Go To Statement Considered Harmful [1] 5. Wait, did this ever happen? :’) I wonder if there’s a modern language practice that extensively uses GOTO [1] https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.p...
- withinboredom 3y agoI use goto whenever I have the opportunity, which, sadly, is not that often. I don't know why people don't like it -- it's essentially an unconditional jump (can replace all while(true);, for example).