4 ms·

I think the let it fails slogan is taken too literally, especially by people who don't use OTP. You can handle errors and exceptions if you want, the superviso

I think the let it fails slogan is taken too literally, especially by people who don't use OTP. You can handle errors and exceptions if you want, the supervisors etc are more here for the unexpected failures that happens for all sort of reasons in any software. Sometimes it also hides bugs because your solution appears to work correctly;)

sangnoir 3y ago
> I think the let it fails slogan is taken too literally, especially by people who don't use OTP I like the philosophy - when taken literally, it saves writing error-handling code at unit-level for an entire class of errors (equivalent to JVMs unchecked exceptions). A well-architected supervision tree will handle that for you, when paired with the excellent out-of-the-box instrumentation for observability. > You can handle errors and exceptions if you want Yes, which is why it's standard to pattern-match on a function's results to check if returned a known err or not - after all, (checked) errors are just a return value in Erlang/BEAM.