Regarding my tweet yesterday about wanting GPU ISAs instead of APIs, Jeff Roberts emailed me with the following comment:
-
-
Replying to @cmuratori
@cmuratori "We *already* ship GL, GL/ES, GL Mac, GL Linux, D3D9 and D3D11 versions. We already have a zillion paths _anyway_."1 reply 0 retweets 2 likes -
Replying to @cmuratori
@cmuratori So I'd just like to reinforce the fact that it would be better_for devs if there were 3 ISAs that we coded to, rather than APIs.3 replies 0 retweets 3 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow No, that sounds like unnecessary complexity I'd rather not deal with. Most would be ok with an API.1 reply 0 retweets 0 likes -
Replying to @pradnelluru
@pradnelluru@Jonathan_Blow You can always use whatever your favorite API is _on top of_ the ISA.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow My thought is that GPU hardware might be too fluid to fix an ISA. And do you want to program each stream proc?1 reply 0 retweets 0 likes -
Replying to @pradnelluru
@pradnelluru@Jonathan_Blow We've already discussed that issue at length.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@Jonathan_Blow Can you point me to a resource?1 reply 0 retweets 0 likes
@pradnelluru @Jonathan_Blow It's in the Twitter feed.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.