Yii2 or Laravel5 compensate for Codeigniter weakness?

Question

I am a web developer, I have been using Codeigniter since 3 years old, and I have used it in many production projects, and Codeigniter was my beginning with the development of projects based on the framework. I later noticed that other flash frames provide many useful features that make life easier for developers, for example:

• Database migration that simplifies and improves database schema performance
• Code generation (scaffolding): that generate a model, view and controller for an object
• Form validation: form validation rules are defined in the generation and in the framework of the rest
• REST API: Supports a REST controller natively within a framework without a third-party plugin.

All of these reasons make me switch to a different framework.

After searching, I found that Laravel5 has the features I need, it also has a large developer community.

My friend uses Yii2, and he recommends me switch to Yii2, also I found statistics, both Laravel and Yii have a good reputation in these statistics.

How Laravel5 and Yii2 differ from others and which added value to each structure

Answer 1

I can only give you the experience that we are here in Sourcetoad :

1) Ready for production: Yii2 follows semver (like the rest of the PHP community / ecosystem), when the structure is fixed, changes are predictable and advertised well ahead of time.

2) Learning curve: here Laravel wins; many more textbooks, cookbooks, web resources and staff.

3) Security: From our experience, Yii / 2 goes higher and higher. Not just customizable, not optional; by default, almost every standard security practice is active.

4) As you noted scaffolding: Yii / 2 wins here. Of the generation of trees, Gii is a light breeze.

5) Community: Although we do not need to over-engage the community in each structure, they are part of the OSS community; however, our initial impression is Laravel may / perhaps push forward. There are no convincing examples.

At the end, the answer: the right tool, the right task .

Answer 2

Introduction

I have been a senior full stack developer for +3 years, and I mainly use Yii for php development. But I was told that laravel is better, so I decided to create an eCommerce Script with laravel to learn more about laravel and see the difference between Yii and laravel.

So what's the difference between laravel and Yii?

in a few words basically nothing, but Yii has a better way to handle forms.

more details

• ease of learning : if you are an experienced developer, it takes about an hour to learn each of the frameworks. and both structures have useful documentation.

• work with rest api : both of them simplify the creation of a REST API, and both have their own path. but I use Laravel when developing rest api because laravel is more useful when developing microservices architecture .

• The developer community may seem like laravel has a wider developer community, but during my career with Yii I did not find a bottleneck in the unanswered question.

• jobs Chances You will be more likely to find work if you are an experienced laravel developer, not Yii.

finally:

it is up to you what to choose, because both frameworks are powerful and useful.

Answer 3

Yes !, Laravel5 or Yii2 has built-in features that Codeigniter lacks.

I have been using laravel for about 5 months for me, it has such strong functions as ORM (Eloquent), database migration, form validation, REST API, HTTP Middlewares and scaffolding (using third-party developers).

I have never used Yii before, so I can’t say about the differences between them, but it also sounds like it has good features. But they say that developers go through four stages:

• No frame
• Use the framework.
• Record your own framework.
• No frames.

An interesting article to read about this link .

These days, all you have to do is grab a bunch of components that work together (relying on each other or working, despite each other), fully load them, configure some routing, connect the configuration system, take out the controllers, process the session configurations and connect to your database.

You can do this completely with random Composer components. But when you wrote this application level ... guess what you did?

You have just created a framework.

Sturgeon, L. (nd). The "Frames" are dead, Long live the Frame. Retrieved July 11, 2016, from https://philsturgeon.uk/php/2014/01/13/the-framework-is-dead-long-live-the-framework/

Finally, there is no perfect answer to your question, everyone uses their favorite option, some prefer to use the framework, some prefer to go as usual. You just stick to what you are comfortable with, and always try to find the best.

Answer 4

No one can answer for you. I think this is a matter of personal taste. I think Laravel has more community, but this is probably for discussion. I usually do this to create a small todo application in different frameworks to see where I find myself suitable.

What I personally like about Laravel is that Laravel also developed Lumen and Spark, which are very useful in their own right. Spark, on the other hand, is a paid job, and it seems to cause a lot of discussion about the future of Laravel.