You don't see "the big deal" about running software in a web stack that you can't look at? I can, and have, dig through every piece of software in my web stack. My grasp of postgres is not strong, but I've set up shop in the Linux, nginx, and JVM source code before and I am much, much more confident in my tools for it.
I don't use IIS either, and for similar reasons. I'm less worried about it on a desktop (and will run Windows or OS X without complaint) because they're not running things for which I have to care about performance or uptime. But for a service, it's non-negotiable.
His "product" is simply nowhere near valuable enough to risk this level of insanity and obfuscation.
Comments
You don't see "the big deal" about running software in a web stack that you can't look at? I can, and have, dig through every piece of software in my web stack. My grasp of postgres is not strong, but I've set up shop in the Linux, nginx, and JVM source code before and I am much, much more confident in my tools for it.
I don't use IIS either, and for similar reasons. I'm less worried about it on a desktop (and will run Windows or OS X without complaint) because they're not running things for which I have to care about performance or uptime. But for a service, it's non-negotiable.
His "product" is simply nowhere near valuable enough to risk this level of insanity and obfuscation.