I believe this is an illustrative image with a simplified view but that is useful so you should leave it. Maybe add a small note saying exactly that: it’s a simplified version of how it works in reality.
NotQuiteLagom
adw632
Ok thanks Jose I’ll take your word for it.
Do you know if it was a recent beam change? My reading indicated it still seemed to be a feature in 2019 that senders can still lose reductions in some circumstances, potentially with remote message sends.
0
josevalim
Creator of Elixir
It has been a while, I would read the major release notes here: Otp 25.0 - Erlang/OTP, Otp 24.0 - Erlang/OTP, etc.
There is a penalty based on the message size but no longer on the message queue of the receiving process.
2
adw632
adw632
Found where they removed that, it was in OTP 21.
OTP-14667
Application(s):
erts
The reduction cost of sending messages is now constant. It will no longer scale according to the length of the receiving process’ message queue.
However there was a change added (exactly as you said) in OTP 22 to punish sender’s of large messages:
ERL-773
Processes sending messages are now punished with a reduction cost based on message size. That is, a process sending a large message will yield earlier than before.
1
arcanemachine
I think of docs vs. cheatsheets like man pages vs. a program like tldr (Funny, that project even has the word ‘cheatsheet’ in the description).
The docs give a broad, deep overview of every aspect of what a module is and how it works, but a cheatsheet is for when you know what something is, but you just need a few quick examples on how to use it. Which, for me, is more often what I’m searching for.
Cheatsheets are hugely underrated IMO and I would love to see them in more places. (I want to use them more myself FWIW, I’m not just asking for free work from others. 
)
4
kwando
Running on 1.16 in a couple of places now, smooth sailing as usual. From raspberry pi’s, my laptop and in the cloud.
Just needed 1 change in one Phoenix app. In one heex template I was calling a function without parenthesis and that failed to compile now 
1
imkleats
If you renumbered Client 3 to Client 1 and vice versa, the overall inversion of the LTR ordering (to RTL) would be inferrable from the numbering, but with the new RTL orientation, the request/response ordering would be correct. But whether the diagram-wide inversion of LTR orientation is equally or more confusing than the partial (request/response) orientation mismatch… 
0
mac-lawson
As a beginner getting involved with Elixir, the code snippets in diagnostics have been a great help.
7
dogweather
Cheatsheets as first class citizens is excellent. I often learn faster by example than from an abstract specification. I think goes for a lot of people.
6