| > This isn’t just academic elegance, it kept phone switches running with five nines of availability. Hmm.... > Erlang is the strongest form of the isolation argument, and it deserves to be taken seriously, which is why what happens next matters. OK I think I know who wrote this. > The problem isn’t that developers write circular calls by accident. It’s that deadlock-freedom doesn’t compose. Is there a need to regugriate it in this format? "two protocols that are individually deadlock-free can still combine to deadlock in an actor system." This is the actually meaningful part. > Forget to set a timeout on a gen_server:call? People have pointed out its factually wrong in the thread. Eh > This is the discipline tax. It works when the team is experienced, the codebase is well-maintained, and the conventions are followed consistently. It erodes when any of those conditions weaken, and given enough time and enough turnover they do. I know this is an LLM tell, but can't point out. It makes me uneasy to read this. Maybe the rule of three? Maybe the reguggeiation of a elementary SE concept in between a technical description? Maybe because it's tryhard to sound smart? All three I guess. I could go on, but sigh, man don't use these clankers to write prose. They're like negative level gzip compression. |