CodeIgniter Does It For Me

Good point cartalot.

Personally I prefer Python, but Php and, __sigh__javascript__sigh__, pay the bills.

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".

Well, the only question directed to you was the following:

How would you compare them speed and memory wise?

Yet, you answered that with a very short sentence and then opted to advertise Laravel's features and trying to come up with reasons why "a lot of codeigniter developers" supposedly hate on Laravel.

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.

And nobody has questioned this, yet you continue to reiterate and emphasise on Laravel's large feature set.

It's fair game to mention it once when comparing, but (as I already said) overzealous advertisement is what makes Laravel really annoying to outsiders.

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?

Here:

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.

This goes beyond (again, the uninvited) listing of Laravel's features and/or stating the larger count. It is strongly implying that CodeIgniter's features are inferior in terms of quality.

A highly biased and subjective statement, to say the least, and there are plenty more reasons why it's not a fair comparison.

I also think it's a little pre-emptive to say I'm talking down to CI devs.

When you tell people that they hate on something, and you tell them that they do so because they're simply not up to that level, you are talking down to them.

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.

So, assuming that it is about territories (which is silly), you choose to provoke that?

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.

I do understand a lot more than that, and I know that you do mean well, but that is beyond the point.
We're just sick of reading about how great Laravel is - it's rise largely caused by aggressive marketing in the first place - and we don't need more of it here.

Sorry, I don't mean to be marketing Laravel here. Just from a purely business perspective, it would be stupid not to realize competition and the benefits of seeing what they may be doing that we're not doing.

I think Laravel is way to bloated in some aspects, and has some good features in other aspects. Marketing has taken them a long ways, but at the end of the day, a working product is what makes or breaks you.

I'm not going to sit here and dissect every sentence in a post, but I do believe that catering to Laravel and talk of other frameworks and not shutting down any positive talk about competitive frameworks would be a good start to possibly inviting new blood into Codeigniter. I'd love to copy some of the best features in Laravel, Cake, Rails, Phoenix.... and have them in Codeigniter in a "CI way". It's easy to have similar features that other frameworks have, but it's difficult for other frameworks to have the simplicity/flexibility of Codeigniter.

I'm sure you see what I just said as not what I was doing before, and if that's the case, I apologize again, but I was just trying to state facts as I saw them.

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

I use CI for it's simplicity.

I have found Laravel a complete PITA to install and configure.

I second that. When I was considering whether to use Laravel or CI, I installed both to try them. After some length of time (I don't remember exactly how long as it was a while ago) I gave up trying to get Laravel to work. I had CI up and running in 5 minutes.

Before using CI I wrote vanilla PHP and did so in an MVC kind of way. However CI has revolutionised my ability to write applications faster and in a more organised manner. It's very similar to the way I was doing things before, just better, but still familiar. For that, I am massively grateful to the developers and contributors behind CI.

Sometimes I can't help feeling like one of the "uncool" kids at school when I read comments from people that have left CI behind and moved on to Laravel. But I think sometimes you have to go with what clicks and works for you. For me it's getting the job done that puts money on the table - when all said and done the client doesn't care what technology is used as long as it works.

Sometimes I can't help feeling like one of the "uncool" kids at school when I read comments from people that have left CI behind and moved on to Laravel. But I think sometimes you have to go with what clicks and works for you.  For me it's getting the job done that puts money on the table - when all said and done the client doesn't care what technology is used as long as it works.

Ah the uncool bit must be most developers who have been in the industry long enough to see their preferred language/framework become "not the latest shiny trend anymore".

I feel exactly the same, the older I get, the more I worry about job ads now asking for Laravel, not CI, but then again a lot of the jobs ask for NodeJS, not PHP so... I am dooooomed either way!

Clients should not worry about tech stack, however you can see how they want peace of mind that there are other developers out there who could pick up the project at later date.