Comments (9)
Conclusion: We should strive to support as a wider range of PHP version as possible.
from queue-interop.
I'd like to clarify that PHP 5.6 is EOL and it receives on security updates - http://php.net/supported-versions.php. I greatly respect those who various reasons can't just simply upgrade their codebase to 7.x, so the question is not to ignore that part of community, but clarify on roadmap: IMO, at the point when queue-interop become a by-law/de-facto standard, even 7.0 will be EOLed, so the question is about future goals rather then today.
from queue-interop.
Symfony 3.0 requires 5.6.
Laravel 5.0 requires 5.6 too
If we migrate we will not be able to use the interop in any of those frameworks which is bad.
from queue-interop.
To give a full perspective,
Symfony 4.0 requires PHP 7.1
Laravel 5.5 requires 7.0
both coming later this year.
AFAIK, Laravel 5.0 is pretty mature and current stable is 5.4. It also have own Queue component which is just nice. Symfony 2.8 (which is current LTS) is also have plenty of queue bundles.
Giving that queue-interop is in it early development/discussion phase and doesn't have enough feedback from community, I would not consider that any mature and production-ready queue library will adopt it at current stage, neither new queue library that implement this interop pop up and gain enough eyes and adopters to be considered as a mature candidate for production use in such projects like Symfony, Laravel, Magento with massive userbase.
To sum up, early adopters naturally are more likely to use more recent PHP (7.x) version than those who will come when interface will be fully ready and will have enough implementations.
from queue-interop.
We already use it in several projects. All projecst are run on PHP 7 though not all use recent Symfony version. The oldest one is on 2.8.
Never mind, that's beside the point.
from queue-interop.
No, it's pretty valid point. While older queue-interop
are still support 5.x it should not be a problem as current users may still use latest stable version that has 5.x support. And the overall question is about future, less likely there is a good reason to drop 5.x support in near future - you can still have a feature branch which will adopt 7.x and port 5.x changes to it.
from queue-interop.
I am afraid it will be way over my head to support two branches at the same time. If some one wants to maintain the 7.x branch I dont mind.
from queue-interop.
I gave a brief look on existent PSR's interfaces and it seems that vast majority of them are really support PHP 5.x (some of them even 5.3). Taking into account widespread of PHP 5.x, if interop want to be real interop it will have to deal with 5.x. I'd personally would love to see new cool features, but maybe some other time. Anyway, let's try to hear from others and keep this discussion live.
from queue-interop.
As mentioned in #9
PHP 5 vs PHP 7:
I saw you discussed the issue here (#2). You decided to go for PHP 5 support a few month ago, but the tide has turned since then. Then newly passed PSR-15 is PHP 7+ only and upcoming PSR will be PHP 7+. So you should definitely target PHP 7 now.
So it make sense to drop php5 support
from queue-interop.
Related Issues (14)
- Setters should return himself HOT 4
- Traits to implement Interfaces HOT 1
- Interface names do not respect PSR HOT 6
- Remove a Message typehint from InvalidMessageException assert method
- Why message body is of type string? HOT 12
- how to change the default directory for the queue storage?
- Master branch more recent than develop
- Drop PHP 7.1 and 7.2 support
- Still maintained? HOT 4
- Proposals
- I cant see why a PsrConnectionFactory interface is needed. HOT 3
- Message creation should not depend on context HOT 1
- Quick review of queue-interop with some comments HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from queue-interop.