Future Improvements
C/Pecl Extensions
Swoole: https://github.com/matyhtf/swoole (https://github.com/ziadoz/awesome-php/issues/108)
SCrypt: https://github.com/DomBlack/php-scrypt (https://github.com/ziadoz/awesome-php/pull/91)
PThreads: https://github.com/krakjoe/pthreads
Graceful/ViolentDeath (https://github.com/ziadoz/awesome-php/pull/118, https://github.com/ziadoz/awesome-php/pull/119)
DoubleMetaPhone: http://pecl.php.net/package/doublemetaphone (https://github.com/ziadoz/awesome-php/issues/102)
Asynchronous Resolver: http://pecl.php.net/package/ares
LibSodium: https://pecl.php.net/package/libsodium
PHPTrace: https://github.com/ziadoz/awesome-php/pull/341
Framework Bundles
SF2 Gearman Bundle: https://github.com/ziadoz/awesome-php/pull/141
SF2 Elcodi and PaymentSuite: https://github.com/ziadoz/awesome-php/pull/140
@ziadoz love the idea of license display.
How to list all framework components? This page would get too long, Am I wrong??
@bordoni I'm not sure if I'll do this yet. I'm concerned it might clutter the list and be difficult to keep track of.
French PHP Resources: https://github.com/ziadoz/awesome-php/pull/334 https://github.com/ziadoz/awesome-php/pull/335
@ziadoz about framework components, why not make a subdirectory of md files, each of them dedicated to a framework and listing components with some infos like the README.md ?
Or those frameworks project their own list you can link to - e.g. awesome-cakephp for CakePHP. Depends on the framework and if they already have their own list. Ideally, the frameworks should own those specific lists, and it will also be less work for you to mainain them (they would otherwise become outdated over time).
https://fatfreeframework.com/3.6/home look at this amazing framework F3. This is the best of the best :-)
Or those frameworks project their own list you can link to - e.g. awesome-cakephp for CakePHP. Depends on the framework and if they already have their own list. Ideally, the frameworks should own those specific lists, and it will also be less work for you to mainain them (they would otherwise become outdated over time).
@dereuromark Linking to separate awesome lists for framework specific bits sounds like a good idea. If you open a PR I'll take a look. Thanks!
Most helpful comment
Or those frameworks project their own list you can link to - e.g. awesome-cakephp for CakePHP. Depends on the framework and if they already have their own list. Ideally, the frameworks should own those specific lists, and it will also be less work for you to mainain them (they would otherwise become outdated over time).