![]() ![]() Some of the libraries you may find, implement functionalities that already reside within Code Igniter, hence re-inventing the wheel. You may get libraries from GitHub but you still need to modify/copy them to the right directory in the right structure by yourself to suit Code Igniter before you can use them. The second reason is, unlike Laravel, Code Igniter does not have a repository for packages that can save you a lot of development time like Packagist. This problem is currently being solved by Code Igniter 4 which is currently in Beta. load -> library ( "nodes/Lib", null, "alias1" ) $this -> load -> library ( "Lib", null, "alias2" ) } } ?> The code in the controller below will load only the library assigned to alias1 ![]() You’ll notice this when you try to load the same class name but in different directories as Code Igniter 3 was built to adapt to PHP 5.3.+ and has a built-in preventive mechanism to avoid clashing of class names. The first reason is its failure to adapt to the new PSR-4 Auto-Loading feature that PHP rolled out. There are only two reasons I can think of so far, that the framework has lacked over the years which prompted people to choose its alternative (Laravel) to it. ![]() I have used Code Igniter for about 3 years to know that it’s core is really efficient and is one of the most simplest MVC framework out there.Īs small and simple as it is, its applications ranges from simple to very complex projects. With it, one can build rich featured web applications in almost half the time required to write the same application in plain PHP while taking care of security issues at the same time. Code Igniter is a simple and yet powerful PHP MVC Framework. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |