I have to this day never seen anything remotly resembling pattern matching to what we have on the BEAM, it’s a misnomer to call it pattern matching in Rust with the perspective of the BEAM.

I have to strongly disagree here. Of course readability increases with familiarity but that doesn’t mean there isn’t significant variation in baselines. The difference is quite clear between languages that value clean, communicative apis and those that don’t, just as there is between frameworks, and code bases.

And I have had the opposite experience, of developers shutting their ears to criticism around readability/clarity because in their view only “objective” metrics like performance, or LOC, etc, matter when assessing code quality.

edit Also should say I think the point that languages having their own domains makes direct comparisons problematic, is absolutely valid, but even, or rather especially those cases illustrate the power of readability. Like many newcomers to Elixir I started with little to no knowledge of parallel computing, and although of course this made the OTP stuff more opaque than, say, the Enum module, the care put into expressing the problem the clear consistent way made it a lot easier to gain that familiarity.

As much as I love it, in my experience aesthetics have been taken to extremes in Elixir in code I’ve had to work to the point where it makes me sad. The biggest (but not only) culprit would be the pipe operator, so I don’t really blame folks from other languages for being extremely skeptical.