ffead-cpp VS faf

You are partially correct, the framework provides an option to change the backend to any engine (embedded, nginx, apache, picov, rust, c, java, d, js, julia, go, crystal etc), the framework provides integration to all the I/O multiplexing techniques available out there. But I would not reject it plainly with just a single line, more so because "I have built it", whereas for you, you totally have the right to do so, but I would request you to go through the code and also look at areas you may not have browsed earlier and provide any other critical comments you might have missed earlier, that would provide a comprehensive critical review of the framework which will definitely help me improve upon the framework

Trust me, these guys are insane and go to really extreme levels and use optimization techniques which are not generally prevalent among the general programming fraternity. for eg, look at pico.v it is awesome and just-js is truly unbelievable, then there is faf, most of them combine low level programming trickery to reach those insane numbers. Also some of the code may not be useful in a production app but they actually extract the juice out of the metal at every instance. Memory optimizations, compiler optimizations, postgresql wire implmentations, rust black magic, these guys are really crazy and passionate.