WERE MULTIPLE RETURN VALUES GO'S BIGGEST MISTAKE?

Summary from the TLDR Web Dev newsletter

Go's multiple return values create unnecessary complexity because they aren't true tuple types, making it harder to store and pass function results. This design choice negatively affects error handling, concurrency, and generic programming, leading to workarounds like defining custom structs. A better approach would have been using proper tuple types, which could improve Go's consistency without breaking backward compatibility.