CodeIgniter Does It For Me

I feel a lot of codeigniter developers that hate on laravel have been in the CI world too long and just hate on things they don't necessarily understand because they haven't expanded outside of their world. Things like queues, migrations, task scheduling, and validation are all far more advanced than anything in CI3 but might be advanced for a lot of CI3 devs.

- Going out of your way to tell us how awesome Laravel is - check
- While doing so, belittle CodeIgniter - check
- Talking down on a large part of the CI community - check

Hmmm ... say why do a lot of "CI3 devs" hate on Laravel again?

Older CI community members could in fact have a few more reasons to hate on Laravel, but it's this kind of attitude that invites the hate from all other non-Laravel developers. You need to stop shoving it down people's throats.

@Narf
My apologies if I came across that way. I'm a CI developer firstly and laravel when I'm told to. I was simply answering the question asked to me, and as Killishan says in the post above, there are several things in Laravel that are considered "nice".

I know I'm not wrong in saying that Laravel comes with more features than Codeigniter, but that doesn't mean it's better, it just means it's different. I consider myself unbiased when it comes to php frameworks, after all, they are just tools to create what you want to do, and for some cases one is better than the other.

I really want to know where I belittled Codeigniter though. I think it's pretty clear and concise that one of the main features of CI is having a small footprint and high performance, which is exactly what I stated in my first sentence, and Laravel is known for all of it's built in features, which is also what I stated in my post. If you meant belittling because I said it has less features, aren't I right?

I also think it's a little pre-emptive to say I'm talking down to CI devs. It's perfectly natural to be standoff-ish to new territories when it comes to programming. If I started talking about erlang and functional programming, many programmers here would probably be a little lost and that's natural. CI is geared towards a different kind of developer, and you being main person who has to deal with devs trying to help you on Git, I think you would understand that more than anyone.


@Killishan
I agree. I'm not a huge fan of template engines and ORMs being built into the framework. I've consulted on several projects that have front end frameworks or are just rest api servers and it's added overhead. Also, if it's required, it's fairly simple to add those features to CI or any other php framework.

Middleware is interesting, and it has really grown on me. It's cleaned up my code quite a bit and helped some of my team members understand things quicker.

When it comes to the other features we talked about, you're right, it takes 10 or so minutes to write some of that code, but when you're under contract and can't copy your code from one place to another, it's an annoying task to rewrite the wheel everytime.

I'm excited to see what's in store for CI4 and hope to be able to contribute in some way.

All in all, I'm not bashing Laravel or Codeigniter. Any decent developer should realize that every framework might be better for one task or another. Personally, I prefer Codeigniter when I'm going to be building a super custom application where I need to understand and tweak every little detail for my clients, but I prefer Laravel when I'm doing something more mainstream and will be heavily scrutinized in an enterprise. That's fair, isn't it?

Codeigniter is simply one of the tools you need to learn to be a successful developer. Always add more tools to your coding arsenal!