Well, for one, because FluentAssertions is still under active development. I'm trying to get some fixes and improvements in place so that I can release version 1.5 soon.
My two most important goals are to make sure that your tests are intention revealing and that, when one fails, you don't need a debugger to figure out what went wrong.