This is exactly the pattern that Erlang handles the best: 1. Expect you call to os.Open to not fail 2. Then do stuff with it 2bis. Or the running process will

This is exactly the pattern that Erlang handles the best: 1. Expect you call to os.Open to not fail 2. Then do stuff with it 2bis. Or the running process will crash, the error logged, bad state won't mess up the flow and a dev can always hot-patch it