Thread

CodeIgniter has a future, I can assure you.

BCIT is taking over the project to provide stewardship, continuity, hosting, and to foster ongoing community involvement. This is not meant to be “just a student project”.

The codeigniter.com domain is being transferred to BCIT. Once complete, the informational website on ellislab.com will redirect to the new, improved, whiter and oranger than ever codeigniter.com, and the forums on ellislab.com will be “archived”, in favor of the new ones I have setup on my server - necessary because of account privacy on ellislab.com.

At that point, I will be posting a news/blog item about the vision/planning for the project, and inviting the community to participate.

I have been developing and teaching webapps, using CodeIgniter for the last five years. That covers a dozen or so I have built on my own, and over 200 that I have mentored or overseen the development of. I am passionate about CodeIgniter, as are many of you!

James Parry,
CodeIgniter Project Lead

good news, I am developing my project “startbbs” with CI. hope CI3.0 can be released soon.

Sorry… Was pretty deep into a bottle of wine last night when I wrote this. Haha

Honestly.  Much too late, way too late.

CI is great, for legacy applications.  Anything newer, there are far better options.

Some of us, even threw away CI because we out grew it and developed our own (much faster and much better) frameworks.

Unless the “new” version of CI encompasses all these things:  https://philsturgeon.uk/blog/2012/12/5-things-codeigniter-cannot-do-without-a-rewrite .  You won’t really get back the following you once did.  It’ll just be for those that really don’t know any better or are incapable of learning better coding standards/practices.

You should also bear in mind to trash the unreleased version 3 (which is crap by the way - yes Narg that means you) and clean up the irc channel #codeigniter in freenode.  Kick narg out as he struts around like some omnipotent being who is utterly clueless.  You may find that the online community may grow as a result.

Finally, why bother?  If you look at Quora, Reddit, Stackoverflow and other such places when people ask questions about what framework to use.  Everyone recommends either Laravel or Symfony.  Never codeigniter.  I really hope you guys didnt pay too much for it.  Doesnt really seem to make sense to dig up a dead horse to beat it.

Oh and one more thing.  Maybe go back to a much more open license.  One of the reasons why people left was the debacle of the license version 3 was going to have. 

Perhaps if you have this new project being much more open?  Maybe someone can take the project and actually do it real justice.  Bring it up to PHP 5.6 and beyond standards and actually code the framework properly and not to a poor mans version which narg did.

Oh and one more thing.  Maybe go back to a much more open license.  One of the reasons why people left was the debacle of the license version 3 was going to have.

Yes, I want popular permissive open source license like BSD/MIT.

CodeIgniter has a future, I can assure you.

BCIT is taking over the project to provide stewardship, continuity, hosting, and to foster ongoing community involvement. This is not meant to be “just a student project”.

The codeigniter.com domain is being transferred to BCIT. Once complete, the informational website on ellislab.com will redirect to the new, improved, whiter and oranger than ever codeigniter.com, and the forums on ellislab.com will be “archived”, in favor of the new ones I have setup on my server - necessary because of account privacy on ellislab.com.

At that point, I will be posting a news/blog item about the vision/planning for the project, and inviting the community to participate.

I have been developing and teaching webapps, using CodeIgniter for the last five years. That covers a dozen or so I have built on my own, and over 200 that I have mentored or overseen the development of. I am passionate about CodeIgniter, as are many of you!

James Parry,
CodeIgniter Project Lead

Sounds good. Although Codeigniter is light years behind some newer stuff, I’m excited to hear what you guys have in store. Please stay in touch.

@no1youknowz

Some of us, even threw away CI because we out grew it and developed our own (much faster and much better) frameworks.

Much faster? Much faster? Which one? Where? Are you the Phalcon’s author?

You should also bear in mind to trash the unreleased version 3 (which is crap by the way - yes Narg that means you) and clean up the irc channel #codeigniter in freenode.

The unreleased yet version 3 is the best code that this project shows at the moment. Either you are in a deep delusion, either you mislead the others intentionally.

@no1youknowz

Much faster? Much faster? Which one? Where? Are you the Phalcon’s author?

Who mentioned Phalcon?  It’s not exactly hard to develop something faster than codeigniter.  Jeeze.  What your problem probably is.  Is that you could be one of those guys who KNOWS php or develops in codeigniter.  But doesn’t do anything than just adding onto a CMS. 

I actually found CI to be limiting in what it can offer.  I have around 10 composer packages with my application I previously built ontop of CI.  I added in autoloading, namespaces, extended many of the CI libraries, hacked around with the core.

You do realise what a framework is right?  CI is really nothing special.  It was great at the time, but now its days are firmly pass it.  It’s not THAT difficult to code a framework.  There are only a few simple basic components you need.  I don’t even use 80% of what CI comes bundled with.  In-fact if I were to go to laravel it would be the same case.  A lot of good developers have their own libraries in their toolbox.  Oh thats right, thats why I made my own framework.

The unreleased yet version 3 is the best code that this project shows at the moment. Either you are in a deep delusion, either you mislead the others intentionally.

There lies the problem.  The best code for an outdated project.  Who here is delusional now?

It’s alright.  You are probably supporting your favorite framework.  You don’t want it to die.

I’m interested to hear what the intentions are for the project going forward.  But I’m not holding my breath on this one.

@no1youknowz

It’s not exactly hard to develop something faster than codeigniter.  Jeeze.  What your problem probably is.

I can. You said much faster. Phalcon is to be known to be about twice faster than CodeIgniter, so, your creation could be somewhere between. This is not much faster, the benefit is not enough.

It’s not THAT difficult to code a framework.

Wrong.

There are only a few simple basic components you need.

Wrong.

I don’t even use 80% of what CI comes bundled with.

Strange. Maybe your projects are quite simple even for a minimalistic framework as CI.

The best code for an outdated project.

By “best code” I objected the word “crap”, which is wrong.

Wrong…

Oh I’m wrong am I?  Very funny.  Perhaps you just don’t know how to code one.  You know, there are some developers out there who know how to code.  CI is just a bunch of php code.  Have you been extensively though it?  I have.  It’s not that difficult you know.

Strange. Maybe your projects are quite simple even for a minimalistic framework as CI.

Nope, its not simple at all.  Why would I have bothered to extend CI and its core to the extent that I did.  Before moving onto my own framework? 

Codeigniter minimalistic?  Ha!  Good one.

Dude, just give it a rest.  You clearly don’t know what you are talking about.  You are trying to defend a project which clearly you love.  But most have left.

This is my last reply to you.  So enjoy working on that for now dead framework 😉

You realize “no1youknowz” is just trolling you? Clearly he/she isn’t a CodeIgniter developer they just troll this forum to stir up stuff and to get people onto “their” favorite framework. It’s a shame people that don’t even use the CI framework still hang around like it’s a old girl friend they can’t get out of there mind or something? That they stalk to see who she’s going out with now and what is she up to without them. That they put down at ever chance they can to justify themselves. The way a real man handles it is just make your decision and “move on” enough said…

None the less I do use CodeIgniter and look forward to the update.

dmyers, you are absolutely right.

I don’t think that codeigniter has the most up to date features like Laravel, but it still has it’s place. Many products were built on codeigniter so there will always be a place for there to be updates.

Jim - I’m thrilled to see where your guidance brings CodeIgniter to.

For a full-stack PHP framework, even today, I think the things that CodeIgniter has going for it are:

* performance
* simplicity of use/maintainability

Yes, I think there are things that could be added and refactored. I think a lot of the things that Phil’s article touched are are good things, but, quite frankly are not necessary things.

Autoloading is wonderful to use, but CI has always been on the declarative end of the declarative/hidden-magic spectrum. I would love to see it PSR-4 namespaced and added to packagist for easy installation. Integrated with Composer is a must (remove that thing about the command line from the ‘about’ section!). It would be simple to classmap the existing CodeIgniter code. Though if you’re namespacing, it’s done for you there. The Loader could even be integrated into Composer for the heavy lifting, since it already generates fast classmaps when you use the optimize flag.

Basically, I think it’s very possible to keep the simplicity and maintainability while updating it to more current standards. Frameworks like Laravel get so complex in the layers upon layers that they lose some of what they were originally brought about for: developer ease and enjoyment. Don’t get me wrong, I’ve used Laravel and Symfony both and they’re both very good frameworks, but they’re both “enterprise-level” frameworks and what most of use these frameworks for is NOT enterprise-level stuff.

When you start going through all of those layers with coding best practices that were developed around compiled-languages, not interpreted languages, things get slow, so you have to rely on a bunch of tricks and hacks and additional layers to make them snappy again. I do think that many of these best practices are good, but in interpreted-language development, I think we have to find the middle ground that keeps performance while still being maintainable. For the most part, CI does a fair job at that, it’s just gotten a little old around the middle and needs a good workout. 😊

1) Please kick or ban “no1youknowz” .. trolls are not usefull in any way .. dont feed them ;o)

2) Thx to JLParry for your first information. Im looking forward to the new CI plans and roadmap.

3) I use many Framworks but i still use CI for projects because its fast, simple, easy extandable and powerfull. (We are doing webdevelopment and not software dev .. in that case i would use C++).

So .. i believe CI has a great Future.

Just advise Ci plus some new features or rewrite like Yii 2 based on PHP 5.3 and above to enhance the performance.

Best wishes for CI.