I happened to see in the technical-steering-committee repository that Laminas MVC is going to be archived and its development will stop. But I haven’t seen any information about this anywhere else
Can you please announce the future development plans for the Laminas MVC package. A large part of our platform is based on this architecture. Will the development of this package be stopped? And do I need to migrate to Mezzio?
Does Mezzio have the power and flexibility of Laminas MVC and is it recommended for migrating enterprise and in-progress platforms? What will happen to Service Manager? Is it compatible with Mezzio?
An announcement of the final plan and schedule is very useful considering the several months required for the migration
I feel that the timeframe provided is somewhat tight, especially when we need to migrate huge apps from MVC to Mezzio. PHP 8.5 is due to be released in November 2025, which from what I understand is the date where MVC will be considered abandoned.
Is there any possibility you might postpone this date a bit longer to give us some extra time? Please note that we are in the beginning of summer in the northern hemisphere and people are expected to be out of the office during the summer.
I’m almost positive that it will not be marked as abandoned until after it has got support for 8.5. Which means that SMv3 will need to have been updated to 8.5 as well. From what I understand a hard date has not been decided upon. Every decision I have seen the Laminas TSC members make has always erred on the side of giving users plenty of time to migrate etc. Just consider how long the ZendBridge component was around.
So I suppose one would technically have as long as 8.5 is supported to migrate.
Also, I know several folks are working on publishing some articles on migration tips etc.
As long as your applications are modular really the only real friction points are going to be your events, event listeners, controllers, controller plugins etc. Most laminas packages can be used in Mezzio. It would even be possible to migrate your events and event listeners with some planning. Although, not sure why you would… Guess it depends on what they do. Feel free to hit me in Slack if you would like to discuss any of it. I have the same username there as I do here.
Download numbers are not everything, interest has generally declined. There are fewer questions, enquiries and feature requests from users on the subject of laminas-mvc.
The main reason is that there are “no time and resources to maintain it”, what is the guarantee that Mezzio is keeping its updates? It is a bit disappointing for me, because i was far along with a pretty big application in MVC and I can now start with a new (maybe some shorter) learning curve and reprogram and test the application. I don’t want to get in the same situation next year or in a few years, why choose Mezzio, with the risk on lack of support, and not another more popular framework?
I think that these go hand-in-hand with the investment being made on the actually component. For quite some time now, Mezzio seems to be the shiny new toy and the primary focus of the group. New users are directly or indirectly being advised to use Mezzio for their new project which in turn leads to more inquires, questions etc.
On the other hand MVC has been around for years, is battle tested, there is a lot of content out there on how it’s working, and it kinda feels easier to get started. (MVC architectures are being taught in universities for years)
Comparing mezzio and laminas-mvc on packagist shows that both components are being used, but MVC get 7x more downloads. Even if we agree that MVC needs to sunset, shouldn’t there be a straightforward path to drive all those new downloads/ users to Mezzio?
I agree with Jilco, if MVC stop, some companies will switch to another framework.
Why not keeping MVC only with bugfix and updated with new future new version of PHP? I think most of companies that using MVC don’t need new features. Maybe you can open a kind of bounty?
For Mezzio and its related packages, ( not only in Mezzio GitHub organisation, but also in Laminas org), there is “time and resources to maintain it”.
Because there are companies, like Apidemia , which invested (and is currently investing) time and resources in extending the concept of middleware, in Mezzio and middleware ecosystem, having Mezzio as its core, since 2017.
Zend Expressive (the precursor of Mezzio) was launched almost 10 years ago, and it was since then something different and easier to use then MVC design pattern, suitable for modern web architecture.
The good news is that Mezzio microframework with its handlers can be used in a MVC application, implemented step by step. No need to rewrite a Laminas MVC application from scratch in Yii or whatever.
I was a diehard advocate for maintaining the MVC up until the first day I actually started learning Mezzio. That has been… nearly 2 years ago now and not once have I regretted making the move to Mezzio and middleware/handlers. It is so much simpler but at the same time much more powerful than MVC.
There is no question that Mezzio and support for it will be around for years to come.
It’s built using the MVC structure, but we add support middleware, PSR-15, and other modern standards. I believe migrating it from MVC to Mezzio should be straightforward, but having a sample guide would be very helpful.
Also, an important question:
Which components have been retired or deprecated?
and
Do we have an official migration guide available?