Jarrett

Well, it's nice that the beam seems to handle a lot of the problems with letting it crash.

You know, it just goes again or there's a supervision tree and things watching each other.

And I don't have to think about it very much.

I can't think of like an instance in development where I was like, this is really useful, but I'm sure you could come up with one.

Kind of the opposite philosophy that Go took as I write some Go code and I write some Elixir code where with Go, it's like handle every error condition right after you potentially raise one and make sure that it's, there's no error.

And if you're not dealing with it, then you're not writing robust software.

And the other philosophy is let it crash and deal with it elsewhere.

I think they're both legitimate depending on what you're building.

Well, that confuses me.

So how does Fly know about it then, if it's just happening inside of Varnish?

Okay, so where is Fly involved in that?

Because Fly is aware because I see all these Fly notices and I get the Fly emails.

So Fly as a platform can actually reach it and kill that process without...

Killing the machine, rebooting the VM or the firecracker or whatever.

So Gerhard has presented us a multiple choice quiz.

A is 20, B is 40, C is 80, D is 160.

Now I know that I personally receive an email every time this happens.

And so I have a little bit of a feeler into this.

I delete them, so I can't go do a quick search.

Adam, do you get emails when these fly things crash?