Must be some kind of caching optimization and not really something that saves CPU cycles
But then thinking: you'd expect constant double quoted strings to also get this treatment, so single quoting still gets you nothing.
All the above is void without benchmarks.
That doesn't no longer holds true when comparing a non-interpolated double-quoted string and the identical single-quoted string
Tho as others have said, if you're interested enough in optimization to worry about what type of quote you're using, you should just use opcode caching (APC) which will optimizing string parsing along with everything else.
I can type the => character in one keystroke using emacs, though my key combo does technically contain two keys. I could reduce it to one if I really wanted to.
(And I might, because I just found an entire redundant key on my Kinesis keyboard that I never use -- the one right below the X key. Thank you for prompting me to look for such a key. To an emacs user, finding an entire spare key under a finger is like striking gold.)
Similarly, I found that Ruby doesn't use ; as often as :, so I swapped the two when in Ruby mode.
That said, I don't like the arrow operator either, but it has nothing to do with typing. It has to do with the other side of ergonomics: Visual clutter when reading. In a similar vein, the array() operator is my pet peeve: tons of redundant characters, even if you invent a macro for typing it.
Is there any way this could be true except that they went out of their way to slow down single-quoted strings? How could it possibly be slower to do fewer steps?