CI 3.2 - does it worth it? |
Outside the recent fun from our Terminator, I would like to ask what would be the fate CI 3.2 branch. Wouldn't it be better if some new features there to backported to CI 3.1? I think that nobody would be interested about CI 3 with a BC break.
Also, maybe for CI 3 minimal required version of PHP might be bumped up - 5.5 or 5.6. There is no point about maintainig compatibility-layer code and wasting time and strength for too old and insecure servers.
I am inclined to think of 3.2 as serving to make the jump to a supported version of PHP. PHP v5+ EOL'd at the end of 2018 and PHP v7.2 EOLs at the end of 2020.
Jumping to PHP 7.3 might be enough of a BC breaker to warrant a (dot)2.
Or another idea. Maybe 3.2 with a BC break about exceptions would make more sense if it serves as "bridge" to CI 4. I mean some features to be backported from CI 4 - the debugger, spark, the same look and feel. Even I think a MX-compatible addition (the so called modular extensions, people are complaining about it) would add enough value.
I like the idea of full reliance on exceptions. Is that what you are thinking?
|
Welcome Guest, Not a member yet? Register Sign In |