Is CodeIgniter development dead?

#61
[eluser]jonez[/eluser]
[quote author="gdweb" date="1397715356"]On this page: https://github.com/EllisLab/CodeIgniter/...milestones

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

So, why it isn't released ?[/quote]
Did you read Narf's posts? Four posts up he says it's feature frozen and they are ironing out the remaining issues.

#62
[eluser]Narf[/eluser]
[quote author="jonez" date="1397733195"][quote author="gdweb" date="1397715356"]On this page: https://github.com/EllisLab/CodeIgniter/...milestones

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

So, why it isn't released ?[/quote]
Did you read Narf's posts? Four posts up he says it's feature frozen and they are ironing out the remaining issues.[/quote]

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.

#63
[eluser]albertleao[/eluser]
What is the problem with sessions in CI 3 now?

#64
[eluser]jonez[/eluser]
[quote author="albertleao" date="1398275626"]What is the problem with sessions in CI 3 now?[/quote]
I know you guys want a release asap, but continually asking the status and asking the dev's to reply just slows them down.

#65
[eluser]kyoujin[/eluser]
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.

#66
[eluser]albertleao[/eluser]
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.

#67
[eluser]kyoujin[/eluser]
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 ;]

#68
[eluser]ivantcholakov[/eluser]
@kyoujin

The right way for speeding up ORM is just not using it. :-)

#69
[eluser]skunkbad[/eluser]
Straight PDO or Doctrine DBAL for me. ORM is crap.

#70
[eluser]koreldan[/eluser]
[quote author="Narf" date="1397734230"][quote author="jonez" date="1397733195"][quote author="gdweb" date="1397715356"]On this page: https://github.com/EllisLab/CodeIgniter/...milestones

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

So, why it isn't released ?[/quote]
Did you read Narf's posts? Four posts up he says it's feature frozen and they are ironing out the remaining issues.[/quote]

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.[/quote]

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.


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.