https://github.com/Overv/outrun

https://www.youtube.com/watch?v=Q7pgDmR-pWg

>Also, crashes are statistically rare events on arterial and local roads, so it can take years to accumulate sufficient data to establish a valid safety profile for a specific road segment.

That is exactly what this article is about.

On my laptop I had to switch from Firefox to Chrome because it kept filling up all of my RAM resulting in other applications crashing.

Source: https://gs.statcounter.com/browser-market-share/desktop/worl...

You can check anything with a linter, but it's better when the language disallows you from making the mistake in the first place.

>You can forget to use `with` in Python, I guess that's also C now too eh?

When using `with` in Python you don't have to think about what exactly needs to be cleaned up, and it'll happen automatically when there is any kind of error. Consider `http.Get` in Go:

resp, err := http.Get(url)

if err == nil { resp.Body.Close() }

return err

Here you need to specifically remember to call `resp.Body.Close` and in which case to call it. Needlessly complicated.

>Then stop writing spaghetti and use a higher level abstraction like `x/sync/errgroup.Group`.

Why is this not part of the standard library? And why does it not implement basic functionality like collecting results?

You have to put thought into such things as:

- Did I add explicit checks for all the errors my function calls might return?

- Are all of my resources (e.g. file handles) cleaned up properly in all scenarios? Or did I forget a "defer file.Close()"? (A language like C++ solved this problem with RAII in the 1980s)

- Does my Go channel spaghetti properly implement a worker pool system with the right semaphores and error handling?