Thread

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

@InsiteFX is right about that.

EllisLab announced on 9th July, 2013, that they are looking for a new owner. I think they had enough time to take a decision.

If they desn`t publish any news or release v3, until 9th July, 2014, I will leave CodeIgniter and I will searching for a new framework.

I am starting to agree.  This lack of information makes me nervous.  I think they could say something!!  Next week I am going to DrupalCon and really considering using Drupal 8 as a framework replacement to Codeigniter.  I don’t see Drupal 8 being left behind.  You know it really sucks when you develop a product in something and feel like EllisLab’s does not care.  I know we use it for free and understand that, it is more like a friend who is ignoring you.

Come on EllisLabs…..Say something we are giving up on you!!!!!

Believe me, we’d like to speak about it as much as you’d like to hear about progress, unfortunately we aren’t in a position to make public comments yet. We’ll be happy to speak openly about the entire process, but it will have to be after the fact.

Believe me, we’d like to speak about it as much as you’d like to hear about progress, unfortunately we aren’t in a position to make public comments yet. We’ll be happy to speak openly about the entire process, but it will have to be after the fact.

Will this happen by the end of this year (2014 :D)?

Believe me, we’d like to speak about it as much as you’d like to hear about progress, unfortunately we aren’t in a position to make public comments yet. We’ll be happy to speak openly about the entire process, but it will have to be after the fact.

Will this happen by the end of this year (2014 :D)?

If he could comment on that, he’d probably be authorized comment on a lot more.

There are a lot of outstanding issues on github… maybe offer some of your time to help close them if you want to see progress? 😊

CI 2.2 was released!!! My congratulation!!!

Unfortunately…  ( fortunately for me ) I’ve moved on to using Composer and Slimframework as my basic router.  Best decision I’ve made, now I have the freedom to pick n choose what components I want to use instead of being stuck with a full stack framework and beholden to the creator of said framework for updates.

It was not a decision that was made lightly as I have numerous projects written in CI and really wanted to continue using CI.  But learning how to properly use PSR compliant libraries and develop within FIG standards has made me a much better developer.  I suggest that many of you look into this as well.

Unfortunately…  ( fortunately for me ) I’ve moved on to using Composer and Slimframework as my basic router.  Best decision I’ve made, now I have the freedom to pick n choose what components I want to use instead of being stuck with a full stack framework and beholden to the creator of said framework for updates.

It was not a decision that was made lightly as I have numerous projects written in CI and really wanted to continue using CI.  But learning how to properly use PSR compliant libraries and develop within FIG standards has made me a much better developer.  I suggest that many of you look into this as well.

how so , how has it made you better and how was codeigniter holding you back?

For those wondering about transition to a different framework, I can offer my knowledge of Laravel.

I still code heavily in both codeigniter and laravel, but after learning the features of laravel, there simply is no comparison.

Codeigniter gets the job done and there’s nothing I can’t do with it, but with Laravel, everything is simply easier.

Composer is already baked in and many new packages are written in composer with optional packaging services to integrate even deeper with laravel. The eloquent orm is beautiful and easy to use. The application structure makes a lot more sense. The ease of debugging is much higher.

One thing I’ve noticed now that I am proficient in both Laravel and Codeigniter is that I’m writing significantly less code on Laravel than I would on Codeigniter to do very similar things. Also, Laravel right now has an unbelievably active community and the framework is so heavily tested that it gives me a much larger sense of comfort.

I’m not saying codeigniter isn’t tested, as I know it is, but with Laravel, not only is the framework thoroughly tested, but new packages that are coming out are being thoroughly tested with Laravel first to make sure it works. This makes it much easier to develop things quickly.

If you want a list of some reasons I prefer the Laravel distribution here you go:
-Eloquent / Query Builder (I use PHPActiveRecord with my CI project and there is no comparison)
-Blade Templating
-Integration with composer (with the services and providers)
-Debugging tools
-Application structure
-Adherence php 5.5+ features that make coding much much easier
-Artisan (command line tool for testing, querying a db, route testing, and scaffolding)
-Routing system (Now that I’m used to it, I much prefer a stricter routing method compared to CI’s magic auto router)

I follow Taylor Otwell and a few other php developers on twitter and it’s fun to see them and the heads of php discussing best practices and how to implement them into their systems in the most efficient and non-breaking way.

@albertleao, which version of CI are you talking about?

@albertleao, which version of CI are you talking about?

One of my major applications is running on CI 2.2

My laravel application is on 4.2

@albertleao, which version of CI are you talking about?

One of my major applications is running on CI 2.2

My laravel application is on 4.2

I never tried CI 3 develop branch and I’m just curious to know if the gap you talked about between CI and Laravel would be somehow filled by that version.

@albertleao, which version of CI are you talking about?

One of my major applications is running on CI 2.2

My laravel application is on 4.2

I never tried CI 3 develop branch and I’m just curious to know if the gap you talked about between CI and Laravel would be somehow filled by that version.

No, not at all. It’s too massive a jump and Laravel uses newer methods that don’t fit in CI.

Thanks for the info—Just inspired me to actually start my first Laravel project rather than just talk about it!

Is CodeIgniter development dead?

No. Closed.