Open JimTools opened 8 months ago
Hmm, but what if somebody wants to create a new app that should also be compatible with older PHP versions?
I guess theirs an argument for both side, if you creating something new then newest language features are preferable and the performance gains form newer versions.
But if you’re constrained by your production environment would also be nice to have that option.
can you can tell I’m in the first camp, if your making something new use update things it also means you can make more assumptions as a maintainer (rightly or wrongly.)
Ultimately this is a decision is for the maintainers.
What I'd suggest (yes, not a maintainer) is: if you want to drop something, drop 7.4. But not everything until 8.3. I'm using the latest Linux Mint distro, based on Ubuntu Jammy, I think, and there I've 8.1, I think. So please don't make the latest version of this package useless/hard for people just using the php version of their distro.
A skeleton is simply a starting template for developers to build their applications from, but it should encourage them to leverage the latest tools. Keeping it aligned with the latest PHP version makes sense to me.
Those who prefer an older version can always roll back to a previous commit that does support that version.
With the recent... ish release of PHP 8.3, I think the project can bump the version. this wouldn't break backwards compatibility as the skeleton is only used to create a new Slim App and would also allow for other packages to be upgraded.
Supported Versions