Oh, one of the Phoronix articles we had in on the past (some years ago): Less facts and more guessing. Why would one do that?
Announcement
Collapse
No announcement yet.
Qualcomm Mentions "Vulkan2" & What I Would Suspect Of "Vulkan 2.0"
Collapse
X
-
-
Good/Interesting Articles = Interesting Stuff To Test / Write About && Not Feeling Burned Out / Tired / Headaches && (Good Ad Rates || New Premium Supporters)Michael Larabel
https://www.michaellarabel.com/
- Likes 1
Comment
-
Originally posted by waxhead View PostI take on your bet Michael! No Vulcan2 for 2018 and I get premium for life. If I lose I'll purchase premium for life. Deal or no deal?!Michael Larabel
https://www.michaellarabel.com/
Comment
-
Originally posted by cRaZy-bisCuiT View PostOh, one of the Phoronix articles we had in on the past (some years ago): Less facts and more guessing. Why would one do that?
- Likes 2
Comment
-
Here's what I think Vulkan should have: A mid-level graphics API (like Apple's Metal). This would lower the barrier of entry for Vulkan, and make a smoother transition from OpenGL. Given how slow Vulkan adoption is going, I think there needs to be a middle option which is significantly faster than OpenGL, but within reach for more developers.
Comment
-
Originally posted by Michael View PostSure, deal, assuming you mean Vulkan 2 and not 'Vulcan'
Anyway, I thought I'd seen drafts of upcoming Khronos standards, but perhaps they only make them available on a case-by-case basis. I poked around in their github account, just now, but didn't see anything that was obviously vulkan-next. Presumably, it's a private repo, if there even is one.
I'm guessing their meeting minutes are also non-public...
Comment
Comment