Well that is good news. For what it’s worth this latest news has earned you guys the benefit of the doubt from me at least.
I’m still not ready to tattoo a monkey on my chest, but I will temper any future criticism in that light.

The only problem with Mono.Simd is that it has only been tested on Intel, and we do not know how well this design maps to other processors. So we first need to implement it in various other processors to understand how well (or bad) the API maps to them and whether Mono.Simd requires changes.

Mono.Simd has continued to evolve since we originally released it. Since it has not yet fully settled, it is not ideal to become part of the standard. It was part of the upcoming standard, but at the committee we decided that it was best to wait.

We need to get Mono.Simd working on ARM, Power, Larabee and a handful of others before we feel that we have a general purpose solution that will work across processors and before we can recommend that it becomes System.Simd.

We have been working with Microsoft on the ECMA Community Promise and the Moonlight Covenant for some time. There was no point in pre-announcing anything, so I remained silent as I did not think I could add any value by beating a dead horse. Instead I went to talk to Microsoft and outlined the problem and the need for a better patent license. Microsoft was very supportive and receptive and the wheels got in motion to get this approved. But it takes time.

As for Moonlight’s covenant, not only we are on the same page, most importantly, Microsoft is on the same page. But things take time.