Comment Eatting your cake and having it too. (Score 4, Insightful) 35
Here's the thing, Intel loves to be the one that sets the standard. They do because it provides them with a dominant position which they can then leverage. However, in order to do that, not only do you need to have an implementation, you need a reason for developers to give a shit about your implementation. If it can't be used for multiple platforms or if it's total shit for non-Intel chips then why the fuck would any developer use it?
Here's what's more likely to happen: Intel will develop it's own partially closed source libraries that are specifically optimized to their chips and nobody will use them.
The only viable alternative (that developer will actually use) is looking at existing APIs/frameworks and submitting optimizations for Intel chips. Doing so means you will not have the dominant position and can't be used as leverage.
Honestly, they could go with the compatibility route and it would be better for more people. However, I know Intel's greed and their greed is telling them to sabotage their own efforts which means later they will be surprised when their code is largely ignored.