Thread

Also, check out this Google trends chart

http://www.google.com/trends/explore?q=codeigniter#q=laravel, codeigniter, cakePHP, symfony, Yii framework&cmpt=q

At this point, it’s hilarious to hear talk by them about “new versions every few weeks”. It has been SO long since there was a new version! Even if 3.0 is stable enough to use on my own websites, can I really take responsibility for coding up a customer’s website in a under-cooked framework? Besides that, the community is suffering tremendously. It’s no longer the cool framework that people are using, and you can tell by the quality of forum posts that the user base is dwindling except for newbs. In order to revitalize CodeIgniter, Ellislab would have to put some real time into it, and they’d probably have to break some backwards compatibility. They’re not going to do either of those things, and so we’ll just have to wait and see where things are in the next year. I anticipate them releasing 3.0 at some point but the PHP community totally rejecting it, and everyone who is serious about development moving on to Symphony, Laravel, Yii, etc, etc. It really sucks, because I use CodeIgniter every day, but feel like I’m going to be forced to abandon it, lest I lose my credibility as a developer. If you primary use CodeIgniter, who will hire you if they know what’s up? Feeling defeated :(

Can’t speak for anyone else, but I use CodeIgniter because of it being so stable and not being updated with useless stuff that I don’t need…. Backwards compatibility is also a huge thing for me… 90% of my customers who use my software written in CodeIgniter are still on PHP5.2+

So if you want to keep your “developer cred” and use the latest and greatest bleeding edge stuff to make yourself look like you know what you’re doing, go ahead… CodeIgniter is not for you. I’m sure you’ll want Laravel… But make sure once you write your code, you don’t have to go back in a year and put in add-ons or update the framework, because chances are the whole framework has changed so drastically none of your code works anymore.

Me? I’ll continue to use CodeIgniter.

People who build website by using PHP they use CodeIgniter(Cl).That means it’s an open source Website Application Development Framework. CodeIgniter lets you creatively focus on your project by minimizing the amount of code needed for a given task.It means that it takes less time to develop a professional project with CodeIgniter framework.It has so many advantages:

**CI is lightweight and extensive
**CI is easy to learn, adopt and deploy.
**Easy handling and customizing.
**CI Offers flexibility and easy management With MVC based framework.
**Active Record Implementation is simply superb and easy to remember.
**Provides easier configuration and customization of configuration files.
**CI facilitates easy working with a variety of developers.
**And what not…......

But Cl has lot’s of disadvantages, that’s are folllows:
**CI’s PHP based only and not very object-oriented in some parts
**CI has PHP4 legacy code.
**CI is company-driven instead of community-driven.
**Its irregular releases.
**Framework itself has no built-in ORM(Object-Role-Modeling)

So.decision is yours,how will become benefited to use CodeIgniter for a website development…..?

Greetings Everyone,
I have seen many similar “Is CodeIgniter dead?” discussions in recent months.

For myself, I have been using the excellent ProcessWire CMS for most of my projects.  I still do have a need for a good framework for many projects.  I have tried Laravel, Cake, and Yii.  But for whatever reason, nothing feels as natural to use as CodeIgniter.  I WANT to keep using CodeIgniter.

I believe it would make a huge difference if EllisLab just communicated what’s going on.  If you look at usage statistics, CodeIgniter is still the most popular framework.  There is just anxiety among many users about how it’s going to be supported going forward.  We know that it is the basis for ExpressionEngine, so Ellis Lab has a lot invested in it.  But what are the details?

I guess what I’m saying is that, like many other designer/developers, I prefer CodeIgniter for many reasons, CodeIgniter is strong, and I want to see EllisLab pull out a good move to get themselves back in the game.

Thanks,
Matthew

I guess what I’m saying is that, like many other designer/developers, I prefer CodeIgniter for many reasons, CodeIgniter is strong, and I want to see EllisLab pull out a good move to get themselves back in the game.

Can’t agree with you more, if there were more updates/news/casestudies on CodeIgniter website, no-one would say, that it is dead.

Even if they only bring back active casestudies section with few words from developers why did they choose CI etc, it would be a good start.

It’s very sad , as i see it’s the end of the lightest and fastest method for coding.
Responsibility is most important part of the open source project . as i see that it does NOT exist on the ellislab’s team.

Thanks,
Siavash

It seems we have to migrate to other frameworks like cakephp and other good php frameworks ...

It seems we have to migrate to other frameworks like cakephp and other good php frameworks ...

You only have to migrate to something else when there is a task CodeIgniter doesn’t allow you to do and that other framework does.

Right on the money, what the hell else do you want (for free) that you can’t find or build yourself?  Greedy little things, where does such entitlement come from?

Opposite to the previous posts, I’d like to add my two cents.

In my opinion CI is just a very mature project. So the question is, do you need a “V3” mark on it or many new features to get your work done or just to keep your trigger-happy soul ehm… happy?

I’ve got a rather long running project, a site built on CI - I couldn’t imagine upgrading it and getting it broken on every corner (google for stories on various other frameworks doing so).

You can implement some new stuff through libraries or helpers, I know, I know - it’s not the same. Rather than complaining - just go for the framework, that suits your needs. Be it real, project-oriented, or imaginary, ego-oriented.

It’s clear that ellislab doesn’t need or want CI anymore. They are killing it slowly and surely painfully for us the CI lovers.

For now I’m struggling about the day after CI, there wasn’t and it will never exist a framework as clean simple yet powerfull, fast and stable as CI.

I hope I’m wrong but RIP CI :(

Being silent is not being dead or going to be dead. It’s just the matter of fact that CI has reached the programmer’s level of satisfaction using the framework. Updates are a little bit of slow for now, because there were no major bugs, and everything works fine. I mean it can’t be dead just because of being silent. And why would ellislab spend their butts making the framework #1 just to drop it down in the future. Stop that false alarm.

If they will make CI open source, then it would be nicer. :D

I like the slowly but surely approach of CodeIgniter.
It is very extendable so you can tweak it by yourself.
In short it is a mature project.

By the way who is the one man guy developing the 3.0 version?

I believe that to survive CI needs to be split into two major branches. One branch that is aimed at those who might have their software run on low budget hosted environments with legacy versions of PHP - currently that would be 5.2.x. And one branch that is aimed at those who are running their own production servers. This would not be the bleeding edge where things break frequently, but a stable and maintained version of PHP that is included in for instance Debian old-stable - currently that would be 5.3.x.

The upside for those that like EllisLab can not require more than a legacy version of PHP is that when the time comes to raise the bar there is a new version of CI ready that has been tested by many.

Ok, I know CI is the most stable PHP framework.

I don’t mind using it as it’s but with some issues to be solved for example the support of Sql Server, CI support is deprecated. we need some fixing for those things nothing more nothing less.

BTW can some of you explain the licencing strategy for CI 3.

regards

Derek Jones explains the new OSL 3 here: http://ellislab.com/forums/viewthread/202562/