When comparing CodeIgniter vs Beego, the Slant community recommends CodeIgniter for most people. In the question“What are the best backend web frameworks?” CodeIgniter is ranked 14th while Beego is ranked 15th. The most important reason people chose CodeIgniter is:
Setting up CodeIgniter is quick and easy. You can download the version you want from the CI homepage or directly pull the latest version from GitHub. After that, you unzip the contents to the directory that's required. The final step is to edit the `config.php` to suit your needs and it's set up and ready for development. There are also a lot of guides and tutorials from developers who have been using CI for a long time. This is because of the relative old age of the framework and the large community behind it.
Ranked in these QuestionsQuestion Ranking
Setting up CodeIgniter is quick and easy. You can download the version you want from the CI homepage or directly pull the latest version from GitHub. After that, you unzip the contents to the directory that's required. The final step is to edit the
config.php to suit your needs and it's set up and ready for development.
There are also a lot of guides and tutorials from developers who have been using CI for a long time. This is because of the relative old age of the framework and the large community behind it.
Pro Well documented
The documentation is clear, structured and thorough. It explains both commonly used and CodeIgniter specific concepts and always with clear examples.
CodeIgniter has a small footprint, just 3MB and that's including the user guide.
Pro Active community
Because it's relatively old and well-liked, it has an active community of developers behind it. It's used by a lot of websites in production.
CodeIgniter is tested by hundreds of thousand of developers that use it in production. This means that it's very hard for any bugs or problems to go unnoticed. Even when a new version is out, bugs are quickly found and patched up.
Pro Open source
The MIT License (MIT)
CodeIgniter is open source and is distributed under the MIT license.
Pro Easy to use templating engine
CodeIgniter has it's own templating engine built-in. It's based on a mustache-like templating language which is easy to learn for new developers who have never seen it. While experienced developers will feel very comfortable using it.
Pro Output caching
CodeIgniter lets you cache the web pages in order to decrease loading times and increase efficiency and performance.
Pro Built in ORM
Beego's eloquent ORM is a simple and fast Object-Relational Mapping which helps with organizing the application's database. Beego examples and documentation all use the beego ORM. No need to learn to use and integrate another ORMs API.
Pro No need to find and install external libraries
Beego is a "batteries included" web framework, which means that a lot of features already come out of the box. This way you don't have to spend time and find third-party libraries to integrate to the framework for most of the tasks you need to complete.
Pro Built-in tool which watches for changes
Beego has a built-in tool which watches the code for changes. This tool (called bee tool) can be configured to run any task once the code changes. It can run tests or reload and rebuild the whole project.
Pro Auto testing
CodeIgniter was first released during the times of PHP 4. This means that a lot of features that were added later to PHP are not available. Some of these features are:
- Support for namespaces
- Modular separation by default
- Procedural function helpers
While nowadays CodeIgniter can be used along the latest version of PHP, these features were not added so as not to mess with backward compatibility. They can still be used with CI, but it requires extending core files to make it work which is a waste of time and energy and requires advanced knowloedge of both PHP and CI.
Con not unit testing
Con It does not have basic functions
Some of the missing features include controller security, filters in forms and modoles, rules of validation, among others.
Con Non-idiomatic code
Con Builds may fail silently
Sometimes even though a build has failed, the pages will still render. Apparently it caches a previous build when the current one has a problem. This can be a frustrating though because it leaves you wondering why the page you are working on stopped working out of the blue.