FuelPHP vs Silex

Fuel has very few restrictions on how to write code. Classes and controllers can be in any file structure, any folder can be the "modules" folder and native classes can be extended any way you want.

FuelPHP is open source and is released under the MIT license.

FuelPHP follows the HMVC pattern which makes it possible to divide the code into smaller modules.

Fuel takes security very serious, and as a result, has implemented the following measures to ensure the safety of your web applications:

• Output encoding in views
• CSRF protection
• XSS filtering
• Input filtering
• SQL injection

FuelPHP is all about being lightweight and simple, this is also demonstrated by it's built-in ORM, it's simple yet powerful. It maps a model to each table in the database, assigns fields on the table depending on the model configuration.

The thing that makes Silex stand out from other PHP microframeworks is the fact that it's built using some of Symfony2's components. Making it quite powerful but still lightweight enough to be considered a true microframework.

Silex is open source and is licensed under the MIT license.

Based on Pimple, Silex has a simple Dependency Injection container that consists of just one file and one class.

Silex makes use of Symfony2's HttpKernel which is used to abstract requests and responses. This in turn, makes it very easy to test apps created with the framework.

By using Pimple, the Silex application extends the Pimple class, which in turn is nothing more than an implementation of the ArrayAccess interface that has been a part of PHP since version 5.0.

This makes it possible to use an instance of the Application class as if it were an array. Like so:

$app = new Silex\Application();

$app['config'] = new Config($config_path);

This gives developers a great deal of flexibility when injecting dependencies and when testing.