Is SO_REUSEPORT really all that much better than a server process that hands off incoming connections to other independent processes via an AF_UNIX socket with

Is SO_REUSEPORT really all that much better than a server process that hands off incoming connections to other independent processes via an AF_UNIX socket with sendmsg/recvmsg? If I understand SO_REUSEPORT right you let the kernel decide everything - access control, receiving process, timing, etc in exchange for not having your own process doing the same thing. Since that simplistic approach is the kind of thing that can be implemented in about 100 lines of user-space code doing file-descriptor sharing with sendmsg/recvmg via AF_UNIX sockets, I don't see the benefit of pushing that complexity into the kernel. Especially since if you want to exercise any greater level of control you'll just have to roll your own AF_UNIX based code anyway.