It's interesting because the author lists some very concrete problems in the way SELinux is implemented in modern distros, but their conclusion - instead of fix

It's interesting because the author lists some very concrete problems in the way SELinux is implemented in modern distros, but their conclusion - instead of fixing these problems - is to disable SELinux completely. Will it really help the sysadmin in the long term? What we need to have is concrete feedback to the SELinux team listing the problems and suggesting the ways to solve them. I believe making the logs more verbose is probably the easiest to implement; working on high-quality and accessible documentation is another; documenting the particular policies implemented by the vendor of a particular distro is a must.