Thanks Pete for the recognition!
I architected this feature to solve a problem of having to maintain different Community Servers having different PHP versions to fulfill a client's particular PHP version needs... This in turn made core maintenance upkeep incredibly difficult due to the differing dependency requirements of each PHP version which added countless hours of overhead keeping each PHP ecosystem up to date... The unification project (PHP MultiLevel or PHPML) was a win/win situation where clients were given the control to select which PHP version they wanted, without having to be moved to a different server which offered what they wanted... At the core level, getting out security and other updates was now much faster due to only having to work on the unified PHP devel tree and corralling their dependencies into more logical groupings... PHPML was neither easy to design or deploy, but all the countless hours of one challenge after another was worth it in the end because we brought something very unique (in the hosting industry) to the table and solidified it for everyone...
On the flipside other hosts (_try_ to) solve our proprietary PHP SecureMode functionality via PHP-FPM, but I can tell you that removes a great deal of control from clients not being able to tweak their PHP runtime via .htaccess file (php_flag, php_value) directives... Our PHP SecureMode is based on the Apache + PHP module which does offer the ability to adjust runtime in realtime...
PHPML was a natural evolution of PHP SecureMode and unified our development models that allow for us to be agile and rapid in server upkeep along with client convenience...
