What do you think if we make fat-free as a PHP extension?
I am sure it will get much more performance as a PHP extension,
It's time to make PHP extension frameworks for these days, look another here: http://yafdev.com/
It's a core PHP framework as an extension developed by a core PHP developerWhat do you think?
Usually I would say something like "fork away" to something like this, but from what I read, this would require a full rewrite of the framework functionality in C?
I am sure it will get much more performance as a PHP extension,I'm not sure the speed advantages would compensate, for example, the lost community involvement since it would then be a C extension (with all it entails, compilation, installation, packaging, etc?) instead of plain php code.
Also, the requirement to have a php extension installed would greatly reduce the possibility of using F3 across a lot of shared hosts.Would developers need to compile their own extension? Apt and Yum repos? pecl install? Can we use composer update? etc etc.
I actually think the opposite, with hhvm, php7+, and dirt cheap computing price these days, i think creating native extensions is much more of a niche thing than an actual overall necessity. Unless you're dealing with massive workloads or trying to squeeze every last cpu cycle it would be more cost effective to get an extra/upgraded server than put another piece of tech/language into your stack. (imho).
Still, if you or anyone wish to implement the F3 api in a native extension I'll surely give it a try since I usually run my own hosts and could install any needed extensions and it should definitely be faster.