(08-27-2017, 12:23 PM)PaulD Wrote: I always think it is a bit unfair to ask volunteers to commit to something that stretches years in the future. If we paid for CI then I could understand it, but since we don't then we should all be a bit wary of the demands we make and the affect it can have on what I imagine is an exhausted, small and stretched volunteer team.
It works, is stable and pretty much secure now. CI4 is not released yet as a stable version, so there is no decision to make, new projects should be CI3.
When CI4 is released, it is not like your CI3 website will stop working. And it has already been stated that CI3 will continue to be supported for security well into the future. Providing plenty of time to play with CI4, experiment, allow to mature a bit, before even thinking about converting existing CI3 sites to CI4.
As for needing CI4, no, maybe not, but you will want it when it comes out I am sure. It is going to be fabulous IMHO, a leap forward, a jump into the wonderful world of PHP7 and onwards. Personally, I cannot wait to start experimenting, but for now, since bills need to be paid, I have decided to wait for the stable release before playing.
So in my humble opinion, there is no question, you should use CI3 for your new projects (correct at time of writing, and probably for some time to come).
Paul
Thank you for the answer. To be honest, I don't really care about new features being added to CI 3 in the future. I care only about security updates with an LTS (long term support) approach. Since you say CI 3's security will be supported "well into the future", are you talking about 6-12 months or 3-4 years? (I am trying to quantify with more certainty, arbitrary words like "well into the future").
Thanks.
