HMVC and Cjax

[eluser]jonez[/eluser]
[quote author="InsiteFX" date="1392058495"]The point is how many more backwards libraries etc; are they going to break? This is why half of the community has already left Codeigniter for other frameworks.[/quote]
Any library that's overloading core functionality should expect to require modifications when a new version is released. You can't avoid that in any framework. If they had used private instead of protected it would be bad, but protected vs public shouldn't cause a problem. From what I've seen they've split a lot of large core methods into pieces so it's actually easier to overload in CI3. The last router update they made reduced my controller suffix mod from two pages to less than 40 lines.

[quote author="InsiteFX" date="1392058495"]The best thing for CI is for them to start from scratch and build a new PHP 5 HMVC framework that is up to date, instead of trying to patch this one up.[/quote]
Wouldn't that be worse? If they did that no existing libraries would work they'd all require rewrites. There are some neat features in the more recent versions of PHP but there isn't anything you can't do today albeit in a more roundabout way. Namespaces (if I needed them but I don't) is about the only feature I can think of that would necessitate using another framework. Everything else is just a newer way to do the same thing. If they did do a rewrite it would alienate all the existing users and for what? There's already 5+ other frameworks out there that fit that bill.

If you're concerned about being 'modern' you should try Node not another PHP framework. Backends are becoming increasingly unimportant, and offline first will be the next iteration of web applications. That's my plan in the long run, today CI isn't much more than a rest server that handles API's. Users only care about the experience not what's under the hood (PHP, Ruby, Python, it doesn't really matter).