Nope, that's what I'm talking about. That article shows how to optimize this constant checking of errors.
What I'm trying to say is that in elixir you handle this at the level of the process. In go the whole thing is one process so you can't do that. In elixir you let it crash, and if the process crashes you report the error and conditions of the crash in the log.
In a real system you would only have a couple things where you do a try/catch or "is error not null" type checks-- for the whole program.
What I'm trying to say is that in elixir you handle this at the level of the process. In go the whole thing is one process so you can't do that. In elixir you let it crash, and if the process crashes you report the error and conditions of the crash in the log.
In a real system you would only have a couple things where you do a try/catch or "is error not null" type checks-- for the whole program.