Good point. But my assumption would be that backslash was chosen because it's a reserved sequence that didn't have a meaning yet. E.g. they could have started suddenly treating "It costs $x, where x is the number of rides" as a compile time error when it previously was a perfectly valid string literal. And not everyone wants to introduce yet another string literal syntax like ES6 does with backticks...