Loops must die
A good developer will always try to enlarge their toolbox and get to know new or better tools for specific situations, but it's also helpful to free yourself from mental ballast now and then to get rid of one or another stone wedge. For most developers, a classic loop is such a stone wedge. Marco Emrich dives into why you shouldn't program loops anymore.
| Talk Title | Loops must die |
| Speakers | Marco Emrich (codecentric) |
| Conference | O’Reilly Open Source Software Conference |
| Conf Tag | Fueling innovative software |
| Location | Portland, Oregon |
| Date | July 15-18, 2019 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
A good developer will always try to enlarge their toolbox and get to know new or better tools for specific situations, but it’s also helpful to free yourself from mental ballast now and then to get rid of one or another stone wedge. For most developers a classic loop is such a stone wedge. Marco Emrich dives into this not entirely uncontroversial assertion from different angles, including the problems and application scenarios for loops. He asks if there are alternatives, what the advantages are (spoiler: high-order functions like map and reduce, recursion, etc.), and if there are any situations where the classic loop is still preferable. You’ll then examine loops and the alternatives in various languages (e.g., JavaScript, Java, Haskell, C#, Ruby, and PHP).
