CodeIgniter vs. Divi

The input class makes it easy to provide server-side validation and scrubbing of user input. Setting Error messages. It doesn't require constant command-line access, It's great because it has a strong community and excellent documentation, but the problem is that it tries to retain backward compatibility with PHP 4 and therefore lacks a lot of "standard" features modern frameworks have such as auto-loading.

Incentivized

Divi is great if you build multiple websites for clients; however, I'm not sure it is cost-effective if you only make a single site.

Incentivized

• CodeIgniter is an excellent tool when a simple database API is needed. Postgres, MySQL, and SQLite are all abstracted into a simple-to-use
• CodeIgniter's simplicity is truly its best feature, because you are able to create controllers and methods based on the http://www.example//, and immediately being developing the application.
• Flexibility is also another developer-friendly feature, because developers are able to design their application in any way - controllers, models, libraries, and helpers can be located anywhere or not used at all.

Incentivized

• It has a very easy-to-use and extremely complete block editor.
• It offers many templates that you can use as a base for your website.
• Customer service has been fast and effective whenever I have needed it.
• Tiene un editor de bloques muy sencillo de usar y extremadamente completo.
• Ofrece muchas plantillas que puedes utilizar como base para tu web.
• La atención al cliente ha sido rápida y efectiva siempre que la he necesitado

Incentivized

• Faced some issue of session management, so that's why we used the Core Session library for that. It would be great if we could improve it a little bit.
• Frameworks provide the option to setup all getters/setters, so having this option in it is a great idea.

Incentivized

• The load time of the builder could be faster. On some websites it takes a long time to load, and may crash the page. (I believe they've said they're working on this stability issue.)
• Warnings on updates if they're difficult for some sites to run. I have one website that has crashed more than once from Divi's theme updates. I always back it up before the update so I restore the site, but this is still a bit of an inconvenience.
• Integrated (or more clearly marked) tutorials within the builder. I migrate site maintenance and ownership to clients after the site is complete and some could use refreshers within the builder on what happens where i.e. the difference between a section, row, module.

Incentivized

Divi is overall a great tool to use - I think I would need to spend a little more time to dig into the tool to provide more long term feedback.

Incentivized

CodeIgniter has a very small footprint. The source code is very small sized. Setting up a project is very easy. Follows MVC pattern. Consumes low memory and CPU. Well documented. Has a built-in forum for users to discuss and get the solution for issues. Periodically updates versions and patch fixes etc.

Incentivized

I find Elementor very clunky and find Divi much more intuitive.

Also we purchased a lifetime license for Divi and can use it on unlimited websites, while Elementor there is a yearly subscription per site

Incentivized

• Because of quick turnaround on portals/intranets, it was easy to offer this as an option to clients.
• As there is no cost associated with this framework, it was great not having to worry about purchasing or licensing. (MIT License).
• Community support helps in that there are no ongoing support contracts or costs.
• No direct representative for one-on-one support, if needed. This can cut into time used on projects.

Incentivized

• Higher conversion rate
• Theres no needed more tools
• Ive got rid of a CTA tool since with Divi i can make them. Is not that easy, but is functional

Incentivized