Interesting to see the dual MIT-Apache license approach. I'm less familiar with Apache, but what does it offer that MIT doesn't? Is it just to allow downstream projects and forks to choose which of the two licenses they prefer? If so then the GPL is curiously missing.
Apache license has some language around patent grants that some people want and other people don't like (e.g. apache isn't compatible with GPLv2, some of the BSDs reject it, ... and some people just think its too complicated). Thus offering both makes both sides happy is my guess.
