Agreed about the case insensitive search.
Concerning the casing in expressions, at first I was a little surprised that expressions wouldn't change automaticly the case of variables or object names.
When eye-scanning the code, it is easier to pair objects and variables through lines if they all use the same casing (the one of their definition).
It's not a big deal though, as long as the expression works and pick the right object/var.
Jayjay your example probably works for seasoned developpers who take naturaly into account that Player is not PLayer. It is less user friendly though when you have to look for hours in your code trying to find out why there is an error and that the player object is affected instead of the layer.
"OH myyyyyyyyy I just made a typo and haven't seen it before."
This happens often ^^
Insensitive casing prevents that case.