Yii3 will not be what I expected

I am a yii2 fan. Yes, despite many of its shortcomings, I was able to love it and for about 5 years I have been earning bread and butter thanks to its developers.

For about two years now I have been waiting for the release of Yii3. I expected it to be a cool monolith, like the second version, but heavily modified and with new buns. But, as it turned out, Yii3 is taking a completely different path.

Yii3 has a telegram channel https://t.me/has_yii3_released where every day at 10:10 a post is posted with the current state of Yii3 development. I noticed that after 5 months after I subscribed to this channel, there was practically no development. Then I decided to write in the framework chat (https://t.me/yii3ru) with a proposal to contribute your work to the development. Because I am still “nedomiddle”, then I was politely sent to learn testing (no sarcasm, really polite).

And then I decided to ask how strong a competitor it can become laravel. To which one of the admins answered me “I don’t know, but technically it turns out well :)”

BUT! Then I was told that (I am me, A is the admin of the channel)

A: yii3 itself does not provide architecture, you can scatter anything as you like, but there are application templates that offer some architecture

Then I had a question, why is a framework needed then if it does not provide architecture?

A: It provides infrastructure things: routing, logs, middleware, cache, etc.

And the architecture of the application can be anything at all, that’s the beauty.

Me: how to figure it out (for me, a freelancer) if the people in the project decided to make some kind of architecture of their own? Maybe I’m dumb, but I don’t get the point. Why is this? Doesn’t it look like just a bunch of libraries installed via composer? will the level of immersion in the project for programmers increase?

A: Well, in fact it is – a set of libraries

I answer:

Well, I see the conditional order “finalizing the project on yii2 / laravel” – in this case, I already know what is where and where what to look for. For the studio / company that use the framework in the project, it will be easier to find a developer, and the developer will have a minimum of time to join the project. Isn’t that the point of any framework – to define a clear architecture?

Admin response:

A: Applications are different and the architecture in them may be different. Ideally, the architecture of the application should not depend on the framework at all.

Why am I all this: it seems to me alone that the more strict the architecture, the lower the entry threshold for the programmer. who are you hiring? And so it is easier for one developer to understand the code of the project he came to? I believe that this is the beauty of frameworks – to provide an architecture, a basis, thanks to which a new developer on a project can join development with minimal costs. And with Yii3, on the contrary, there will be an increase in the entry threshold and problems for everyone.

I myself am a freelancer, and it is very cool when on a project with yii2 / laravel I do not have the documentation for the site / application, but I know where and what to look for. (documentation is cool, but very rare). But here comes Yii3, which allows you to build your own architecture, while it offers only a set of packages. I’m not really a fan of laravel, but, apparently, soon I will have to completely go to it, because on yii2 there is less and less work.

Unsubscribe, please, how you feel about this. True, I will not be able to answer myself because my karma at the time of this writing allows me to leave only one comment per day, and after its publication I most likely will not be able to write at all. Therefore, for a good reasoned dialogue, I’m waiting in a personal. Thank you all for reading!

Similar Posts

One Comment

  1. While I fully understand you in having some sort of rope to swing along, the power of leaving the architecture fully open to the devs is a huge benefit. I’ve been building two projects with Yii2 and loved it. Looked into Yii3 and didn’t understand it at first, because it feels so loose/borderless. But that is exactly its strength.
    The same happend with Vue2 evolution to Vue3.
    Loose coupling – how programming paradigms suggest. Modular structure.
    Its a good long term invest in agility.
    Laravel in its state today will soon or later die the Yii 2 way, because it has its borders that aren’t to overcome with plugins and therefore prevent the development of future web-apps that need the flexibility to adapt to new web-technologies.
    I look at it this why: You don’t have a framework anymore, but you have your application consisting of different libs/middleware wired together. No bloat of unnecessary code/deps.

Leave a Reply

Your email address will not be published. Required fields are marked *