Thread

On this page: https://github.com/EllisLab/CodeIgniter/issues/milestones

We can see:  v3.0.x -> 100%

So, why it isn’t released ?

Did you read Narf’s posts? Four posts up he says it’s feature frozen and they are ironing out the remaining issues.

On this page: https://github.com/EllisLab/CodeIgniter/issues/milestones

We can see:  v3.0.x -> 100%

So, why it isn’t released ?

Did you read Narf’s posts? Four posts up he says it’s feature frozen and they are ironing out the remaining issues.

Excluding session-related ones, the existing “issues” are 99% edge cases, feature requests and general discussions. I’m only working on CI_Session, anything else is irrelevant.

To answer the question though, we simply don’t use the milestone management in GitHub.

What is the problem with sessions in CI 3 now?

What is the problem with sessions in CI 3 now?

I know you guys want a release asap, but continually asking the status and asking the dev’s to reply just slows them down.

Well, Laravel did a good social programist campaign picking all this people (being symphony in disguise). I really feel bad around things that are happening around CI, as its very powerful tool, but I m personally attracted to projects like PhalconPHP. Of course usually requires dedicated access and works with newest PHP but future belongs to C driven PHP frameworks. And it works magic. And is very similiar in approach to CI (or not, as its very loosely coupled)

But if I ever had to work on server where i cant install Phalcon i would still go with CI.

Phalcon is a really interesting framework.

I personally chose Codeigniter 3 years ago for my startup. It has helped a lot but I have definitely run into some speed bumps along the way which I have now learned is because of it’s older code base. In the end, I still launched my application with many users, a front end for a desktop, mobile, and phone app, and a backend that handles all 3 versions of my application on codeigniter; All of which is hosted up on Amazon AWS and uses composer packages.

I love it and it’s great but I’ve had to tweak so much of the system that I’m completely married to the Codeigniter framework and will need to do a lot of code review and testing when upgrading to 3.0.

Still a great framework, I think a lot of us are just wondering what the future holds. I’ve grown accustomed to using Composer + Packagist, ORMS and other features that simply aren’t super easy with Codeigniter.

I installed PHPActiveRecord via Sparks and love it, but when you compare that to some of the new ORMS out there like Eloquent for Laravel, Doctrine, or ActiveRecord for Rails (I don’t mean to start a php vs ruby war), it’s very far behind.

Either way, the I think we’re all just excited to see what’s to come.

if you want speed ORM is not a way ;]  and u see it nicely in phalcon how much u loose when app footprint form 300kb ( same app on CI was already way beyond 4-5 MB) moves instantly to 500+

and phalcon orm is written in C ;]

@kyoujin

The right way for speeding up ORM is just not using it. 😊

Straight PDO or Doctrine DBAL for me. ORM is crap.

On this page: https://github.com/EllisLab/CodeIgniter/issues/milestones

We can see:  v3.0.x -> 100%

So, why it isn’t released ?

Did you read Narf’s posts? Four posts up he says it’s feature frozen and they are ironing out the remaining issues.

Excluding session-related ones, the existing “issues” are 99% edge cases, feature requests and general discussions. I’m only working on CI_Session, anything else is irrelevant.

To answer the question though, we simply don’t use the milestone management in GitHub.

When a software get stuck on Official development, Open Source community tipicaly fork a semi-affiliated version with those bug fix that official version doesn’t cover for some reason.

In history some software was forked:

Firefox—> Iceweasel
Chrome—> Chromium-browser
Thunderbird—> IceDove
Debian—> Ubuntu(more friendly)—> Mint (keeping something similar gnome2)
MS Office—> Open Office—> Libre Office

CodeIgniter 3—> with ci_session created by community could became—> “CommunityIgniter 3” (?)

Maybe EL, viewing that the fork revive interest in CI, restart developments.

It’s simply an idea.

At this point I don’t think the question should be if development is dead, but if there is a future for CI. I don’t mean a future where a small community sticks up for it, but a future where the professional developer community embraces it, uses it, loves it. Honestly, for me, I’d be embarrassed to say, and would never call myself a “CI developer”, or that it is my coding foundation of choice.

The code is truly legacy in nature, and while fully tested and “fully baked”, the PHP community has mostly moved on. Most modern frameworks are now built with a common structure, and we’re now running websites on PHP 5.5.X.

Maybe the question should be, what can CI do to be the framework most devs want to use?

At this point I don’t think the question should be if development is dead, but if there is a future for CI. I don’t mean a future where a small community sticks up for it, but a future where the professional developer community embraces it, uses it, loves it. Honestly, for me, I’d be embarrassed to say, and would never call myself a “CI developer”, or that it is my coding foundation of choice.

The code is truly legacy in nature, and while fully tested and “fully baked”, the PHP community has mostly moved on. Most modern frameworks are now built with a common structure, and we’re now running websites on PHP 5.5.X.

Maybe the question should be, what can CI do to be the framework most devs want to use?

For veteran and middle skilled developers would be nice to have a frameworks detailed technical comparison without following fashioned new low life frameworks before choosing new one to invest time and money on.

Would be useful also to understand if CI3 innovations are enough to (self or community) implement ci_session to choose this last version for those customer that not have an hosting with SSH access with right permissions or installed libraries on server.

For new entry developer would be nice to understand what version start to study to easily learn only MVC logic with simple, complete and power framework to build firsts or most projects till getting good idea what framework dress better his way of programming on web.

In last case, entry level have to learn CI2 at the moment, having to migrate or rewrite their projects in a future CI3 release.
With a little community implementation of CI3 they could start learning directly on last and more updated version.

The only way CI will ever be like the other newer frameworks is with a complete re-write from the ground up.

What are the new functionality that CI miss to be like others new ?

The only way CI will ever be like the other newer frameworks is with a complete re-write from the ground up.

It can be done. I made my own framework, and some components are from CI. Originally they were mostly from CI, but then found that I liked other components better. For instance doctrine DBAL instead of CI DB. Swift mailer instead of CI email. The one thing I like batter about CI than most frameworks is the routing to controllers, so I built something similar for my routing. For sessions I went with a DB storage only approach. Auth is built in, and most CI helpers were turned into classes. Overall it still has a very CI feel to it, but it’s using Pimple for a DI container, Composer for autoloading, and no attempt is ever made to be compatible with older versions of php. This is just the way I roll, which it think is a pretty modern approach.

So why not rewrite CI? Better now than waiting, especially If CI will ever become popular again. There’s no hope of that happening without breaking backwards compatibility and making something that modern devs want to use.

Also, THE LICENSE! Let’s have MIT or BSD. The license for CI3 is fucking retarded.