As an overarching critique of VLIW, this isn't that bad, but it does ignore a few things: 1. It's not strictly true that there is "absolutely no flexibility in

As an overarching critique of VLIW, this isn't that bad, but it does ignore a few things: 1. It's not strictly true that there is "absolutely no flexibility in scheduling", there are a few techniques that can at least mitigate this issue, such as Itanium's advanced loads and a few others. On the aggregate though, the lack of MLP is absolutely what killed VLIW, especially nowadays. 2. This is true, but IBM's style (which the Mill has adopted) of "specialization" can effectively negate this issue.