Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[RFC] Improve compatibility with legacy versions #30
Because why not… :-)
Now more seriously: This project is a low level lib that is used as a building block for quite a few higher level abstractions on top of it. As such, compatibility (even with significantly outdated versions) is a major concern to me.
Note that I'm not suggesting putting significant amount of work into this. The patch is already here and, personally, I see little harm in supporting this.
Also note that I'm not suggesting we need to keep support indefinitely. Should this ever turn out to be a burden in the future, e.g. because we actually require any new language features or some external lib, then I'm all for dropping support again.
I understand, and I have to accept it, but I don't agree with it. Also, Composer has a large existing user base still running on it. Is that really the same case here? Cause, supporting it to "reach a larger audience" really doesn't seem like the right reason to me. Anyway, just my 2 cents. You can't blame me for trying :-(.
@alcohol I think you're raising a very valid point here.
Personally, I wouldn't endorse using legacy versions and encourage everybody to upgrade to supported versions for various reasons (new language features, performance improvements, security support etc.).
Despite this, I don't consider pushing (or condoning) anybody my business.
Being a long time contributor to this project, I do, however, consider helping advance and improve this project to be my business. And unless there's a compelling reason, I don't see why these improvements should only reach a part of our user base, excluding a (reasonable sized) portion of our existing users, stuck on legacy versions.