In a case statement, the condition part (when ...) in the branches do not have the same length in general, and especially, else is much shorter than the conditions. So when we write the condition and the return value in a single line, they are not aligned, and are hard to read.
Postfix notation does not require then or ;, so it is concise.
The return values from the branches (e.g., "a", "bb", "ccc", "dddd") tend to be shorter and more uniformly lengthened than the conditions, hence they are somewhat close to being aligned naturally, making this easier to read.
We are usually more interested in the return value than the condition of a branch, especially when we are reading someone's code and are trying to grasp what the case statement does or returns.
This notation is closer to case-like conditional notations regularly used in mathematics:
┌ 1 (x = 0)
x! = ┤
└ x (x - 1)! (otherwise)
So it would be easier to read for those who are familiar with mathematics.
I do not necessarily have any opinion in favour, but neither
in disfavour. Kazuki's old comment probably refers primarily
to syntax-wise how the "when" do not align, so on that note
aligned "when" would look prettier. Actually the trailing
"else" is the most confusing part to me; the "when" does not
seem that awkward, even though it is a bit.
It may be interesting to ask matz's opinion nonetheless either
way - if he were to start ruby from scratch, would he opt for
such a syntax; after all we have had other additions such as
endless method definitions or pattern matching. :)
(I for one would love to see case/when become a more "first-class
citizen" feature, where we could query its internal state at all
times, or use different case/when to be combined, a bit like
treating them as objects with specific state and behaviour - but
I guess I should add a new request rather than repurpose
Tsuyoshi's issue here.)