(04-13-2015, 02:07 PM)rtorralba Wrote: I think is not necessary maintain the backward compatibility. Codeigniter has some solutions for deficiencies that php had in the past but not now. For example loader class, for load classes or prefixes use like CI_ to prevent to use same name classes.
Short-term backwards compatibility is how any platform maintains its existing user base, whether it is an OS, a programming language, an API, or a framework. Even if it requires an extra compatibility layer, it is usually worth the extra effort to provide an easier upgrade path for existing users.
The reason for this is simple: if I have to rewrite my existing application from scratch to move from CI3 to CI4, I then have one more reason to evaluate other frameworks and one less reason to stay with CI.
Some other PHP frameworks have resisted providing backwards compatibility, and many of them have suffered for it.
(04-13-2015, 02:07 PM)rtorralba Wrote: I think is enough maintain ci3 fixing bugs and possible exploits and make a new version with the same codeigniter simplicity but using native php.
Given that the end-of-life date for CI2 has been set for 6 months from now, I really don't have any faith in the idea of long-term support for an older version of the framework. While the development time of CI3 has been exceptionally long, the maintenance of CI2 during that time has not been stellar, either (though neither is necessarily the fault of the current developers/maintainers).