|
Top-level
 @mcc (this is 900% exaggerated, but there's a grain of truth) And so you *can* end up in a situation where company's representatives on Khronos do not *necessarily* voice company's opinions or wishes. They are just *there*, saying whatever they want to say; they aren't quite aware of what the engine needs or wants, and vice versa the engine is not quite aware of what they are saying. A gross oversight from "management" I guess. 5 comments
@mcc and then you mix in some pride and hubris and arrogance, like "hey all the cool kids are doing this mantle-like renderer design, who are we to not able to pull this off?", and you start nodding along at the conferences and proudly saying how it's all gonna be cool & cozy.  @aras @mcc My recollections are that it was: ISVs: we hate that drivers are doing all this stuff behind our backs. IHVs: well we have to if the API is going to be usable. ISVs: how about if we do all that work instead? IHVs: ooooh - be careful what you wish for. I mean here's Mantle, look at all that crap you have to do. ISVs: that looks awesome - we're software people, we can handle it. IHVs: <washes hands> Ctrl+H, "mt", "vk", <yes to all> |
Gregory's Server
@mcc And then you also get nuggets like company CEO going onto google IO keynote and promising the engine will ship Vulkan support in "like 3 months", and that's *totally news* to people working on the engine since everyone there is "it's gonna take 3 years to get into a design that suits vulkan". Why would a CEO do that? Because another engine did it, and it's a pissing match between CEOs or something.