It has been a while that I have been working on igniteplate and I haven’t been able to put much time to it. Two days back, I happened to read this. And then I thought of giving Laravel a try.
After being a dedicated Codeigniter developer for so long and even started work on a major project of my own, Laravel was something that took me away.
Analysis: Codeigniter
The pros and cons of Codeigniter.
Pros
- A great framework. Very flexible and you can just write your regular PHP.
- No headaches. Simple configuration.
- Templating is easy.
- Output caching. Increases speed of your pages.
- Brilliant documentation.
Cons
- No auth class to work with.
- Routing is very linear.
- No asset manager.
- Form helper is a little cumbersome.
- Library and 3rd party apps are difficult to find.
Analysis: Laravel
Now let’s see how Laravel is better.
Pros
- Auth class is really great. Uses bcrypt by default.
- Routing and controllers are really streamlined.
- Event queuing is possible.
- Simpler and more versatile form validation.
- It comes with blade templating engine.
- Brilliant documentation.
- Bundle installation and easy upgrades.
Cons
No problems faced so far.
It’s been only some days that I have been working on it and it’s very different from Codeigniter. It will take me sometime to get the hang of it. I am liking this framework a lot.
Dilemma
After I have started working with Laravel, I realized that a product like igniteplate is something that can be made with Laravel in a much lesser time. The only reason I wish to continue working on igniteplate is that it hasn’t been done on Codeigniter. And I am sure some developers like myself will benefit for me. Also, there is sure a little attachment to this project because it’s mine.