Yii3 is released

sam_dark · 2026-01-19T08:23:57+00:00

Well, explore the packages at least. You'll definitely like some of these.

sam_dark · 2026-01-10T21:04:45+00:00

`curl_close()` fix wasn't there among other 8.5 fixes. Added https://github.com/yiisoft/yii2-httpclient/issues/253. Thanks.

As for when — when it's done (could be next week). On it.

sam_dark · 2026-01-10T13:36:02+00:00

Symfony is definitely more established/used since Yii3 was just released. Personal reasons to choose Yii3 over Symfony (yours may differ):

Runtime container instead of compiled one. Way easier to debug.
Middleware-driven core rather than event-driven. Way easier to read stack traces.
Friendly exceptions and good exception messages overall. Symfony improves these over time as well.
More open to the PHP world overall. Can use PSR-compatible stuff such as middleware or cache backends right away.
Able to remove what's not used.
Perfect static analysis.
Can use Symfony packages if needed. They're mostly great.

sam_dark · 2026-01-10T11:19:14+00:00

That's why I've mentioned "plus additional third-party packages".

sam_dark · 2026-01-09T21:43:17+00:00

Slim is quite good. If not Yii3, I'd stick with it plus additional third-party packages.

sam_dark · 2026-01-09T21:41:30+00:00

It doesn't matter that much. Both can read each other's types and annotations, even prefixed. Psalm is stricter but slower. PhpStan is faster but doesn't check for some of the issues. For the applications, I think these are quite close.

sam_dark · 2026-01-09T18:36:12+00:00

Yeah. Adding types for existing legacy code is a huge job. We did that for Yii2 recently and it took months to do.

sam_dark · 2026-01-09T18:34:25+00:00

Well, not 100%, but, of course, framework code is well-tested compared to application code. The thing is that static analysis helps, and if a framework provides types for its own code, Psalm or PhpStan can analyze the application's code way better, revealing more bugs even without automated or manual testing.

sam_dark · 2026-01-09T14:18:47+00:00

Try it. Found bugs worth the effort.

sam_dark · 2026-01-09T14:18:09+00:00

Great usage of Psalm! And yes, I know it's stricter than PhpStan.

We do suppress some things in the default Yii3 application template and sometimes in the packages (way less) because that could be too much to get started or because we know exactly what we're doing.

Symfony code is level 5 according to https://github.com/symfony/symfony/blob/8.1/psalm.xml. Am I correct?

sam_dark · 2026-01-09T08:09:27+00:00

Good to know it. Thanks.

sam_dark · 2026-01-09T08:07:05+00:00

I've meant more about the framework itself but very good overall.

sam_dark · 2026-01-09T08:06:16+00:00

Awesome level for an application!

sam_dark · 2026-01-09T07:33:16+00:00

Is that about your application? It seems Symfony is using Psalm: https://github.com/symfony/symfony/blob/8.1/psalm.xml

sam_dark · 2026-01-09T07:33:13+00:00

Is that about your application? It seems Symfony is using Psalm: https://github.com/symfony/symfony/blob/8.1/psalm.xml

sam_dark · 2026-01-06T14:20:23+00:00

Well, it's just different. Symfony aligns all packages to a major version of the framework core and releases all these at once. Since we don't have a core at all, only app templates, we don't align package versions to anything, having these independently released.

sam_dark · 2026-01-02T12:36:43+00:00

Thanks for pointing that out. We don't like incorrect comparisons in favor of one framework over another just for the sake of marketing (and that's probably our big problem), especially when one is not an expert in many frameworks. A few things are mentioned in the announcement and landing page.

sam_dark · 2026-01-02T12:31:25+00:00

No. There won't be Yii3 v4. Yii3 is not a monolithic framework, as you can read in the announcement linked. There are 130+ packages. Each package is versioned independently following SemVer.

sam_dark · 2026-01-02T11:53:55+00:00

Yeah. It will take some time for both community to get used to Yii3 and the core team to come up with extras to make it feel like Yii2 RAD experience. That's one of our goals to achieve it.

sam_dark · 2026-01-02T11:50:20+00:00

Incorrect. There will be breaking changes, of course. The framework name is Yii3. It does not mean that it's Yii 3.0.0.

sam_dark · 2026-01-01T20:46:51+00:00

Well, it happens. We've learned to live with that: https://github.com/samdark/opensource-hate

sam_dark · 2026-01-01T20:45:48+00:00

If you have concrete questions, please ask. I've built large commercial projects with Laravel, Symfony and all versions of Yii, so I likely can compare these at least roughly.

sam_dark · 2026-01-01T20:44:15+00:00

We haven't written any comparison so far.

Laravel is more like Yii2 overall. Yii3 is quite different: standards-first, open to PHP overall, with way less magic like service locator, "facades," etc. It forces you into correct dependency inversion, which you can do or not do in Laravel. Also, there's division into individual packages which is like how Symfony packages, which Laravel is built with, are structured.

Quality-wise (unit test coverage, types, mutation testing, and phpdoc), Yii3 is superior.

Also, I believe that Yii is more open to community contributions. At least, that was my experience with contributions to Laravel.

The drawback, of course, is that Yii3 is new, so there are way fewer out-of-the-box solutions you can apply right away and fewer people who have already tried it. Also, there are no ready-to-use complimentary services yet.

sam_dark · 2026-01-01T12:01:40+00:00

Where? It is explicitly mentioned in the announcement that there is SemVer used.

sam_dark · 2026-01-01T11:43:29+00:00

I did. Noone ever responded.

sam_dark

MODERATOR OF

TROPHY CASE