Yes.  I know.  However those places also aren&#x27;t aggressive about upgrading their Erlang versions unless there&#x27;s a critical patch, and even then sometimes those are back-ported by the places creating, maintaining, and deploying their Erlang systems&#x2F;software (such as one of my previous employers).<p>Additionally, these changes are largely superficial, not functional.  They&#x27;re in the &quot;make it pretty&quot; part of the &quot;first make it work, then make it pretty, then make it fast&quot; ethos.<p>It&#x27;s purely developer experience focused of course.  The machine doesn&#x27;t care what order the arguments are in.  Well that may not be entirely true.  I&#x27;d have to look more closely at the function-head matching implementation to see if there&#x27;s some benefit or hinderance in putting non-scalar types first in the argument list... but that would be in the &quot;make it fast&quot; part that comes later ;-)