Switching from CodeIgniter or not?

Question

CodeIgniter

Hello dear!
Now there will be a lot of books, please read my doubts carefully and help me decide whether to leave CI or not.
Essence of the question: I have never been a fan of ORM and other developer consoles, I have always liked and will like the minimalism of CI, because it has the most necessary things. But the question of transition arose again. To be honest, I DO NOT WANT to switch because
1) CodeIgniter is faster than everyone and everything. Only pure php is faster. Well maybe some more microframeworks...
2) Free architecture: you can execute SQL queries in controllers with impunity, call functions that are in the model when generating some block in views, use helpers, do not use helpers, connecting third-party libraries usually does not cause any problems, url routing is simple, understandable and it works clearly, if you want Russian CNC - know the problems, etc. etc.
3) Working with the database. All more or less complex queries are written by hand. Every little thing like "SELECT * FROM table WHERE `ololo` = '1' AND `lalala` = '123'" CI allows you to do 1-2 lines of code.
Yes, I am aware that CRUDs must be written by hand, and to be honest, I don’t quite understand how they can not be written by hand ... well, this is more a question for drupal / yii lovers, and most importantly, I don’t understand the benefit of not writing them by hand, and rewrite for yourself ...
So the question is, should you leave? The thing is that in 2013, in php itself, in principle, little has changed in terms of new features. And it's a feature. That is, for example, projects that will work for 2-3-4-5 years that are made on CI and will continue to be developed will not be taken away from your favorite frame. First of all, by the fact that I do not fully understand what new things to expect from php itself. Fundamentally new. Fundamentally new. Because in the form in which it (php) is now, the latest versions of CI seem to use its functionality relatively adequately. That is, I see the point of moving to ruby ​​on rails, for example, but not with the php projects that I do and plan to continue doing.
I want to hear good reasons for moving. Because I have a feeling that if the project was officially abandoned by the creators, then:
a) it will either stop completely in development, and yes ...
b) the new owners will pull up the reins and instead of a pretty old guy in the world of Linux, there will be full of innovations and new cool glitches version
c) something else
In general, I'm in doubt, comrades.
Share your thoughts in detail, I will read them with full attention. It's like a hint "yes, switch to Yii" - a bad answer. I'm interested in strategy in the context of frameworks. Not tactics.

Answer 1

I don’t understand the benefit of not having to write them by hand

There are many other aspects of working with a database, except for data sampling. ORM is usually tied with a bunch of related features. For example, schema migrations - automatically changing tables to the latest version. Just like how git/mercurial/etc keeps versions of your code, there should also be versions of your database that you can use to roll out updates or roll back. In addition to migrations, there are archives, utilities for filling in test data, and so on and so forth.
If you want to try something new, then try Django. Yes, it's python. For the brave, you can Pyramid. Python itself is very flexible with its meta-programming. You no longer need to generate code files or keep a cache for automatically generated code. There is no global namespace where classes appear in an unknown way, therefore there are no dances with class loaders and it is always clear where and what came from - this greatly increases the clarity of the code. Any objects are self-describing, so that you can get web forms from ORM models, automatic validation, generic views (django view == controller for the rest of the world) and much more. Automatic admin. A good asynchronous framework in the face of Celery. Good management on management commands that are easy to write. Together with Fabric, the headache with rolling out new versions to test and production servers is gone. In general, batteries included.

Answer 2

If everything suits you, if you don’t get sick of his code, then why switch?

Answer 3

When looking for a job, 80% asked about their experience with fireworks, namely yii.
Another reason for the transition is to upgrade your skills, learn new tricks.

Answer 4

I generally dream of learning at least some framework. OOP and MVC knowledge are superficial. decided to learn ci. go out immediately. difficult, although they say you need to start learning from it. I write in pure PHP. how everything works. but. I feel that I lagged behind progress by 10-15 years. teach me(

Answer 5

If you are a freelancer and the customer doesn’t care about technology + you don’t want (and you don’t want) to switch to other frameworks - sit on CodeIgniter, don’t torture yourself - it’s also good. In all other cases, the transition is only a plus. Do not be lazy! Sharpen one more. And you will become an order of magnitude cooler! Forget about Yii - take Zend Framework or Symfony. ..... And in general a strange question: .... to teach or not to teach ..... to work or not to work ... - you decide!

Answer 6

CI is an excellent framework, fast and convenient, if you look only towards Laravel, Symphony 2 and not dull Yii