If you are a member of the Yii team, is it okay to advise people to not use Yii ? I think not. That is totally disloyal. Thatās what I mean. There are things you simply cannot do.It is like a general who has sworn allegiance, but advises new recruits to enlist with the enemy. That is bad.
I am not saying that we are not entitled to voice our opinion. Thatās not the same thing. It is about trust, and loyalty.
Thatās a nicer way to write it, without involving his family.
I personally think that the article was written out of spite and frustration, after a really huge effort on his part and communication issues. Letās try to empathize, and most important of all, move along and be productive.
Interesting. I should have guessed it. Itās not the first time that a member of a team decides to lash out in public after having a disagreement with the rest of the team.
I still stand behind my āFrenchā, though. He deserves a thrashing for breaking that rule. It is so disappointing.
I hope that they figure this out, behind closed doors, as one should.
Thatās interesting:
CakePHP is much closer to Yii than Laravel. There is too many magical mushrooms in Laravel, in my humble opinion
I started reading the documentation for Laravel. I havenāt written a single line of code using Laravel, however from my journey so far, I understand that it contains several layers of abstraction, thus making it slow when seeing the benchmarks. And Yii2 remains one of the fastest.
However, what worries me is the rate of development. It is slow. Issues keep piling up and there are no resources to go through them, not even fix them. If you look at the milestones set in Github, the milestones are many months behind from their initial release date (eg. 2.0.16). I think a development backed up by a company would benefit Yii for the future. Maybe if someone looked for a company to act as a patron for the development of Yii?
My two centsā¦
I also read Paulās blurb in December and to be honest it did stir me into checking out Laravel. As a Yii hobbyist Iāve often thought about the move so during the Christmas period I started migrating a project of mine. After about 5 days into it I stopped as it became clear that although they have the mindshare out there I certainly wasnt āwowedā by it (although their vue.js story is quite good). Admittedly it was based on only 5 days of effort 
So for now Iām quite happy to stick with Yii and see how Yii 3 turns out. From the commits the team is certainly putting in the hard yards so it shouldnāt be too long till its released.
In regards to Paulā¦ From Github comms their appears to be some frustration on his part with the direction of 2.0.x and 2.1 (now 3). I guess when you put a great deal of work into something and things are not moving in the direction (and speed) that you want then it can certainly leave you frustrated. Saying that though my understanding is heās put a massive amount of work in Yii over the years so really the community should be extremely grateful for his effort and wish him all the best. Who knows things change, he may return.
Good comment
But while I am grateful for Paulās work, I am not pleased with (to put it very lightly!) his behavior. It is a team effort - and if you donāt get your way, donāt whine about it in public. It is understandable that team members come and go and have their differences.Things like that happens. Misbehaving is not alright, though.
I am still confident about Yii and itās future. I canāt really off the top of my head point to anything that is as befittingly good as Yii.
Weāre working on it. First step is setting up a foundation with the purpose or funding distribution that disallows spending on anything but OpenSource or Yii needs. It takes time but moves forward.
I would say the same about your behavior. As an active moderator on the official forum of Yii framework, you should really think twice before writing anything - some of your comments may do more damage to Yii Community than one rant of a former core member.
Thatās great to read that. I hope all goes well and soon a solution will be found.
Calm down, guys Weāre here to build stuff we use together so letās focus on it keeping conversation constructive.
There were difficulties and some frustration in the core team but Yii went over it, unfortunately losing Paul who, no doubt, deserves his place in community hall of fame for his contributions. I hope heāll contribute again one day but currently itās not likely.
I sincerely hope that he will - his contributions are great
Yes, youāre right. *crawls back into hole* 
I am kind of āshockedā of Paulās statement. In the past Iāve never felt that Yii is a slowly dying framework or a framework that should not be used for new projects. In fact I am actively trying to promote the framework in our company (with some success).
In my opinion Yii it still the very best framework (that I know) in terms of documentation and flexibility. I also love the explicitness of the Yii that I miss in other frameworks. Iāve once looked into Laravel but quickly decided to stay with Yii (although that was many years ago).
Yii still feels like a āhealthyā framework to me. In fact, Iāve never waited for more than one hour or so for an initial feedback on a new Github issue regarding the framework or the app (thanks to samdark).
Bottom line: I am very thankful for every maintainer of Yii and the community as whole. And I will going to continue to use Yii for private projects for the reasons described above.
I have built a lot of projects on Yii and also Yii2. So I am very thankful for all the core team and contributors.
Iām currently putting in $5 on Patreon, I know itās small quantity but I am willing to contribute more if that helps the development.
Let me know how the foundation goes and I think you should set some goals and ask more individuals and companies to collaborate either with money or commits. Iām sure there are a lot of people who will want to give a hand one way or another.
relax, someday yii2 will die anyway (yii1 still lives btw)ā¦ just be ready for yii3 
Why on Yiiās official site is there no section to attract sponsorship?
itās truly pity, that things with Paul turned out so badly. He was/is one of the most productive core developers for a long time. Paulās article had a little of unethical flavor and was clearly written out due to long-standing frustration with some subjective expectations which did not come true. His intentions were, however, meant for the good of the thing he cared about and for the benefit of the community. Itās truly a pity that core team has not resolved the issue to mutual satisfaction.
Because foundation isnāt ready yet and it will be against transparency to do it improperly.
Paul Who wrote that? Sorry for being sarcastic here, but Paulās way of communicating has been problematic for a very long time. While I also value his technical contributions, the way of talking to people was often rude, offensive and self-opinionated.
I am not surprised about such a reaction when things were not going the way he wanted to.
But Yii is far from dying. So Iāll read this as: He just recommended to move on to Yii 3.
So, the question simply boils down to one simple question: Is Yii slowly dying? It seems to me that it lacks the resources to boost its development rate.
Honestly speaking, I share the same worry with @GoofyX, although Iāve been and will be a convinced fan of Yii framework.
I never question the excellent knowledge and skills of the core team. But what about the time they can spend on Yii 3? It looks to me a little shorter than expected. Itās no oneās fault, of course, but it can really matter. I think we should do something in this respect.
Personally Iām fairly content with the current version of Yii 2 and I can patiently wait for Yii 3 to be finally released. It is mainly because Iām not in the midst of the fast moving current trends of web application development. Yeah, I confess that Iām a bit old fashioned 
Anyway, itās great to hear the voices of you, the core team members and the fellow people who share the love of this straightforward solid practical āhealthyā (Ā© @Coksnuss) framework.