Till what time this poll will remain open? I mean to say when can we see the finally accepted way for namespace
Till what time this poll will remain open? I mean to say when can we see the finally accepted way for namespace
Decision is not going to be made by the poll result, poll should only give an idea of overall preference. Decision should be made based on arguments given.
I think most of packagist packages use CamelCase namespaces, not lowercase.
I personally prefer lowercase (or snake_case) everywhere it is possible for its better readabilty and ease of typing
As said before, lowercase directory names and namespaces make it much easier to distinguish what’s a namespace and what’s a Class.
CamelCase for consistency with other popular packages & frameworks, and because snake_case for multiple words is ugly.
this may not be as important, but php docs also uses camel case in its examples, so it may be a bit confusing for new yii adopters, also concerning multiple word I am in favor of camel case
I’d like to keep lowercase for namespaces. For ease to use and PSR conformity.
That the PHP website uses CamelCase is their problem 
They probably did it before lowercase became the thing, and then keep doing it because they didn’t think to change it.
If Yii goes with CamelCase, then we’ll see naming conflicts, making it both more cumbersome to type and to use.
I’d prefer CamelCase because
The alternative is someCoolNamespace - it should not be less readable than CamelCase since (probably) most of names in your code already follows this convention.
Both lowercase and CamelCase are PSR-compatible. Also I think that CamelCase is used more than lowercase nowadays.
Well, muchmorereadable would be the namespace for MuchMoreReadable. Isn’t that great? 
That way we can tell what’s what at a glance.
But, I don’t feel too strongly about it.
Lowercase for namespaces just matches my policy of always keeping the folders/directories all lowercase for maximum ease of use / cross platform goodness.
First of all I propose to refresh definitions:
So it is necessary to distinguish:
IMHO it is not reasonable to make such a huge change just because of other packages preferred more capital letters.
I vote for taking best of two worlds - camelCase which allows to keep most of the namespaces untouched while fixing readability of multiword names e.g. activeRecord.
This is already current convention for Yii 2: https://github.com/yiisoft/yii2/blob/master/docs/internals/core-code-style.md
- prefer single word namespaces
- if single word isn’t suitable, use camelCase
Wouldn’t that technically be dromedaryCase and CamelCase ? 
I would prefer CamelCase! Because i found my self searching for weird namespaces alias names in order to prevent using two words.
I’m sold with this approach.
Sounds reasonable to me, too.
camelCase is more natural for classMethodNames and classPropertyNames. For class names and their namespeces I would use PascalCase.
Personally I prefer lower case or the camelCase (not PascalCase). But there is an ugly but important point I want to raise is the ease of adopting for new comers. Laravel took a lot of the focuses these years and they used PascalCase. If Yii use PascalCase and when people are sick of Laravel or they simply just want to explore what’s available then Yii will have the edge over those not using because these people will find Yii more familiar.
I know people don’t switch over just because of namespace naming convention and I quite hate to say one framework has to live under the shadow of another framework but small things like this will build up to it’s ‘friendliness’ to the users.
In the end it is namespace we are talking about. It should be relatively easy just to refactor the namespace path during an upgrade and people are expecting changes from Yii 2 to Yii 3 anyway.