SELinux gets a bad rap for being a bit like ed(1). Like ed, SELinux does not overwhelm the novice with too much feedback :) SELinux's answer to everything is EPERM! This can be infuriating when everything seems OK to a POSIX-educated but SELinux-ignorant user who looks at rwxr-xr-x and sees no problem. Disabling SELinux is the solution to a huge range of problems and for that reason most administrators simply disable it as policy.
For my part, I have long looked upon SELinux as the means by which random RedHat insiders screw up otherwise perfectly good software. Probably if it had better logging and meaningful error codes and management tools that can be explained in less than an hour people would look upon it more favorably.