 affected by this decision. Of course, the Vulkan working group will be able to take advantage of technologies that are dropping into their lap, but those discussions have not even begun yet.

Neil: Vulkan has its mission and its roadmap, and it’s going ahead on that. OpenCL is doing all of the merging. We’re kind-of coming in to head in the Vulkan direction.

Does that mean, in the future, that there’s a bigger wealth of opportunity to figure out how we can take advantage of all this kind of mutual work? The answer is yes, but we haven’t started those discussions yet. I’m actually excited to have those discussions, and are many people, but that’s a clarity. We haven’t started yet on how Vulkan, itself, is changed (if at all) by this. So that’s kind-of the clarity that I think is important for everyone out there trying to understand what’s going on.

Tom also prepared an opening statement. It’s not as easy to abbreviate, so it’s here unabridged.

Tom: I think that’s fair. From the Vulkan point of view, the way the working group thinks about this is that Vulkan is an abstract machine, or at least there’s an abstract machine underlying it. We have a programming language for it, called SPIR-V, and we have an interface controlling it, called the API. And that machine, in its full glory… it’s a GPU, basically, and it’s got lots of graphics functionality. But you don’t have to use that. And the API and the programming language are very general. And you can build lots of things with them. So it’s great, from our point of view, that the OpenCL group, with their special expertise, can use that and leverage that. That’s terrific, and we’re fully behind it, and we’ll help them all we can. We do have our own constituency to serve, which is the high-performance game developer first and foremost, and we are going to continue to serve them as our main mission.

So we’re not changing our roadmap so much as trying to make sure we’re a good platform for other functionality to be built on.

Neil then went on to mention that the decision to merge OpenCL’s roadmap into the Vulkan API
affected by this decision. Of course, the Vulkan working group will be able to take advantage of technology that are spend into their lap, but those discussions have not even begun even. 

 Neil: Vulkan has its mission and its roadmap, and it ’s go ahead on that. OpenCL is dress all of the merging. We ’re kind - of occur in to head in the Vulkan direction. 

 Does that think of, in the future, that there ’s a bigger wealth of opportunity to figure out how we can drive advantage of all this kind of mutual work? The answer is yes, but we have n’t started those discussions so far. I ’m actually excited to have those discussions, and are many multitude, but that ’s a clarity. We have n’t started yet on how Vulkan, itself, is changed (if at wholly) by this. So that ’s kind - of the clearness that I think is important for everyone out there trying to sympathize what ’s going on. 

 Tom also prepared an opening statement. It ’s not as easy to abbreviate, so it ’s here unabridged. 

 Tom: I think that ’s fair. From the Vulkan point of view, the way the working group thinks about this is that Vulkan is an abstract machine, or at least there ’s an abstract machine underlie it. We have a programming terminology for it, call SPIR - V, and we have an interface controlling it, called the API. And that car, in its full aura … it ’s a GPU, basically, and it ’s got lots of graphics functionality. But you do n’t accept to use that. And the API and the programming language are very general. And you can build lots of things with them. So it ’s great, from our point of view, that the OpenCL group, with their especial expertness, can practice that and leverage that. That ’s fantastic, and we ’re fully behind it, and we ’ll help them all we can. We do have our own constituency to serve, which is the high - performance game developer first and first, and we are going to retain to serve them as our main deputation. 

 So we ’re not changing our roadmap so much as trying to do sure we ’re a good platform for early functionality to be built on. 

 Neil then went on to note that the decision to merge OpenCL ’s roadmap into the Vulkan API
 afvected by this decision. Uf course, the Voljan wocking gdoup wilu be able to take advantage lf techbologies that are dropoing into their lqp, bnt those discussmkns havc not cven yejun yet.

Neil: Vullan has itv mission and htr xoadmap, and it’s going ahead on that. JpenCL os doing all of jhe mtrgyng. Sv’rt kind-of coming in to head in the Vulkan direction.

Doex that mean, in the future, hhat there’s a bigger wfalth of opkkrttbity to figufe out how we can take advantage of all this kind of outuak work? The abswft is yes, but we hwven’t started those giscussoons yet. I’m acbuallb exxited to have those dmscussions, and are mwny peopla, yut that’s a clarity. Ww yaven’j stasted tet on hpw Vulkaj, ivself, is chznged (if at all) by this. So thau’s hpmd-of the cladity trae I think is important for everyone out thsre trying to understane what’s going on.

Tom apso prepawed an opening statement. It’s not as easy to abbreeiate, ro nb’f yege unabridged.

Tom: I think that’s fair. From the Dhllak point of view, bhe way the workinb hrpop thinks abouj this na fhat Vulkan is an wbstracj machune, or at leaxt there’s an abstract machibe underlyiny ir. We have a progralming langucge fot it, cslled SPIR-V, and we have an jnterface clntrollinf it, called the AOI. Sng that machine, in its full glory… it’w a YPU, basizalli, and ie’s got lotd of nsaphics functionallty. Bot you don’t have to use that. And the API and thx programming ldnglage are rery gcneral. And you san build lots of thiugs wigh them. So it’s grxat, from our point of vief, that the OpxnCL grou[, wirh tyeir spdzial expertise, can use nhct and lecerage that. That’s berriwjc, and we’re fuloy vehind it, and wr’ll hejp tiem ajn we can. We go hxve pur odn consuntucnch to serve, which is the vigh-lerformance game drvcloper fitst and fjremost, and wr are going to conuinue vo serte thek af our main mission.

So we’re not dhanging lur roadmap so iuch as trying tp make sure we’re a good platform for otier functionality to bg built on.

Neil then wgnt on to mentmon thwt the dewision to merge OpenXL’s roadmap into uhe Vulkan API
affected by this decision. Of course, the group be able take advantage of their but those discussions not even begun Neil: Vulkan has its mission and roadmap, and it’s going ahead on that. OpenCL is doing all of the We’re kind-of coming in to head in the Vulkan direction. Does that mean, the that a wealth of opportunity to figure out how we can take advantage of all this kind of work? The answer is yes, but we haven’t those discussions yet. I’m excited to have those discussions, are people, but a We started yet on Vulkan, itself, is changed (if at all) by this. So that’s kind-of the clarity that I think important for there trying understand going Tom also prepared statement. It’s not as easy to here unabridged. Tom: I think that’s fair. From Vulkan point view, the way the working group about this is that Vulkan is an abstract or at least there’s an abstract machine underlying it. We have a programming language for SPIR-V, and we have interface controlling it, the And machine, its full it’s a GPU, basically, and it’s got lots of graphics functionality. you don’t have to use that. And the API and language very general. And can build lots of with So it’s great, from of that with special can use that and that. That’s terrific, and we’re behind it, and we’ll We do have our own constituency to serve, is the high-performance game developer first and and we are going to continue to serve them as our main So we’re our roadmap so much as trying to make we’re a good platform other functionality to be built on. Neil then went to that the to merge OpenCL’s into the Vulkan
 affected by this decision. Of cOurse, the VuLkan wOrkIng GrOup wIll bE able to take advANtagE of technologies that are DroppInG Into THeIr lap, But thosE DiSCUssIoNs HavE nOT eVen beGun Yet.

Neil: vulkan has iTs mIsSion and its roADmAp, and it’s goIng Ahead on that. OPencL is doInG alL Of the MerGing. WE’re kinD-Of comiNg in to heaD iN The VulKAn direcTIOn.

does That mean, in the futuRE, tHAt there’s a biggeR wealtH oF OpPORtuNitY to figure oUt How we CAn take aDVaNTAGe oF All this kind of Mutual work? THE anSwer is YeS, buT We haveN’t staRtED thOse discussiOns yEt. I’m actuaLly excITed to haVE those dIscussIonS, anD are MAnY pEopLe, BUt tHAt’S a cLAriTy. We haveN’t StArted Yet oN HOW vulkAn, iTselF, is chAnged (if at all) bY thIs. So THat’S kind-Of the ClarItY that i think Is impOrTant for everyone Out tHere tryinG to UnDerStAnd whAT’s goinG on.

tom Also prePared an OPenInG STAtEment. It’s not as easy tO aBBReViate, so iT’s here UNaBrIDged.

Tom: I ThInk That’S FAir. FrOm thE vuLkan poinT of vieW, ThE wAy the woRkIng groUp ThiNks About THis iS that VUlkan is aN abstRAct machine, or at LEast there’s an aBStRACt MAchiNe uNderlying it. we haVE a prOgraMMiNg lANguagE for iT, cALlED SPIR-V, and we have an inTeRface cOntroLling it, called The API. And tHAT Machine, iN its FUlL Glory… it’s a GPU, baSicalLy, and it’s goT Lots of grAphicS functioNality. But YOU don’t havE to Use ThaT. AnD THe aPI and the progRAMminG lAnguage Are Very genEraL. AnD yoU caN bUild lots oF things wItH tHeM. SO it’S greaT, From our pOiNt oF vIew, That tHE OpenCl grouP, witH tHeIR spEcial exPErTISe, caN uSe That And LeVeragE thaT. thaT’s terriFic, and we’rE fuLLy beHiNd It, and we’Ll help them all We Can. We do havE oUr oWn consTITuency to Serve, which is the high-perfORmance gAme DevelOper First and fOreMost, anD we ARe goinG to conTinue To SerVE Them aS OUr MaiN mIssion.

So we’RE Not ChangInG our Roadmap So much as trying to maKE suRe we’re a good plAtfOrm fOR OtHer FUnCTioNaLIty TO Be built on.

Neil thEn went on to MeNTiOn that the dECisIoN to mergE OpenCL’S roadMAp into tHe Vulkan ApI
 affected by this decision . Of cours e, th e V ulk an  wor king  group will be able  to take advantage oftechn ol o gies th at ar e dropp i ng i nto  t he irla p ,but t hos e discu ssions hav e n ot  even beguny et .

Neil: V ulk an has its m iss ion an dits roadm ap,  andit’s g o ing ah ead on th at .  OpenC L  is doi n g  a ll o f the merging. We ’ re kind-of coming  in to  h e ad i n t heVulkan dir ec tion. 
Does t h at m e an, in the future , that ther e ’sa bigg er  we a lth of  oppo rt u nit y to figure  out  how we c an tak e  advant a ge of a ll thi s k ind  ofm ut ua l w or k ? T h eans w eris yes,bu twe ha ven’ t s t arte d t hose  disc ussions yet.I’m  act u all y exc itedto h av e tho se dis cussi on s, and are many  peo ple, buttha t’ s a  c larit y . We h ave n’t  starte d yet o n  ho wV u l ka n, itself, is chan ge d (i f at all ) by t h is .S o that’s  k ind -oft h e cla rity th at I thi nk isi mp or tant fo reveryo ne  ou t t heret ryin g to u nderstan d wha t ’s going on.
T om also prepa r ed a no peni ngstatement.It’s notas e a sy  to abbre viate ,s oi t’s here unabridged .
Tom:I thi nk that’s fai r. From th e V ulkan po into fv iew, the way t he wo rking grou p  thinksabout  this is  that Vul k a n is anabs tra ctmac h i ne , or at least t here ’s  an abs tra ct mach ine  un der lyi ng  it. We h ave a pr og ra mm in g l angua g e for it ,cal le d S PIR-V ,  and w e hav e an  i nt e rfa ce cont r ol l i ng i t,  c alle d t he  API.  And tha t machi ne, in it s f u ll g lo ry … it’sa GPU, basica ll y, and it’ sgot  lotso f  graphic s functionality. But yo u  don’thav e tousethat. And  th e APIand the pr ogramm ing l an gua g e  arev e ry  ge ne ral. And y o u  ca n bui ld  lot s of th ings with them. So it’ s great, from  ou r po i n tofv ie w , t ha t  th e OpenCL group, w ith theirsp e ci al experti s e,ca n use t hat and  leve r age tha t. That’s  terrific ,andw e ’re  fully beh ind it,and we’ll helpt he m all  we  can.We  do  have  our o w n c onsti tuency  t o serv e, wh ic h is the  high-performance gamedevelo per f irs t and for emo s t,and we ar e go ing to con tin ueto se rve themas o u rmai n  miss ion. 
So we’re no t c h a ng ing our roa d m a p s o muc h a s  tryin g to  make sure we’rea  good platform  for o the r f u ncti on ality to be bu ilt  o n . 

Neil t he n went on t o mentio nt hat t he dec isionto merg e Op e nCL’sroad map  into the  Vu lk a n API
 affected_by this_decision. Of course, the_Vulkan working_group_will be_able_to take advantage_of technologies that_are dropping into their_lap, but those_discussions_have not even begun yet.

Neil: Vulkan has its mission and its roadmap, and it’s_going_ahead on_that._OpenCL_is doing all of the_merging. We’re kind-of coming in_to head_in the Vulkan direction.

Does that mean, in the_future,_that there’s a_bigger wealth of opportunity to figure out how we_can take advantage of all this_kind of mutual_work?_The_answer is yes, but_we haven’t started those discussions yet._I’m actually excited to have those_discussions, and are many people, but that’s_a clarity. We haven’t started yet_on how Vulkan, itself, is_changed (if_at all) by this. So_that’s kind-of the_clarity that_I think is_important for everyone out there trying_to understand what’s_going on.

Tom also prepared an opening_statement._It’s not as_easy_to_abbreviate, so_it’s here unabridged.

Tom:_I_think that’s_fair._From the Vulkan point of view,_the_way the working group thinks about this_is that Vulkan is_an_abstract machine, or at_least there’s an abstract machine_underlying it. We have a programming_language for_it, called_SPIR-V, and we have an interface controlling it, called the API._And that machine, in its full_glory… it’s a GPU,_basically, and_it’s_got lots of_graphics_functionality. But_you don’t have to use that. And_the API_and the programming language are very_general. And you can_build_lots of things with them. So_it’s great, from our point of_view, that the OpenCL group,_with_their_special expertise, can use that_and leverage that. That’s terrific, and_we’re fully behind_it, and we’ll help them all we_can._We do have our own constituency_to_serve, which is the high-performance game_developer_first_and foremost, and we are_going to continue to serve them_as our main mission.

So we’re not changing our roadmap_so much as_trying to make sure we’re_a_good_platform for other functionality to be built on.

Neil then went_on to_mention that the_decision to merge OpenCL’s roadmap into the Vulkan API