My example was a lazy one, without much thinking. I came up with this one later:
Number of downloads: 29
I posted the link in this topic before. Here it comes again:
The convention for directories is the singular form.
For directories containing non classes files the convention is all lower-case separating words with a dash.
For namespaces directories containing classes files the convention is StudlyCaps.
The examples I see here are with namespaces with just one word which doesn't look awful. IMO, it doesn't look good when you start to have mixing cases.
$demo = new \MyApp\TestDrive\SuperDemo();
$demo = new \myApp\testDrive\SuperDemo();
I don't see how camelCase can avoid problems when deploying in file systems that are case sensitive. I saw people doing this kind of mistakes with whatever convention we may think of. Unless we introduce a new convention where everything is lowercase and write a super new awesome autoloader from the ground.
And we should also avoid arguments making use of the excuse of less tying. I think we all agree that any code is clearer when written the closest to a human readable language even though we are writing for a machine interpretation.
P.S. It is hard to debate in your non-native language