3 ms·
yep... I was just dunking a hobnob while writing some good old imperative C. Did anybody notice that Vulkan, "the future" of graphics APIs, doesn't f*ck around
by vegabook 10y ago
yep... I was just dunking a hobnob while writing some good old imperative C. Did anybody notice that Vulkan, "the future" of graphics APIs, doesn't f*ck around with OO or Functional?
- qwertyuiop924 10y agoWell, that's because nobody except John Carmack advocates FP for the kind of fast code that complex graphics programming requires. And even he says that it should be used in moderation.
- Aaron1011 10y agoAlso, most languages have an FFI mechanism for calling C libraries (if they have one at all).
- bpicolo 10y agoTo be fair, C doesn't really lend itself to either, and a big goal of low level graphics is being performant as all crap
- pjmlp 10y agoHowever Metal, DirectX and the console APIs do. Khronos are the ones that still leave in pure C world. Hence why most researchers went to CUDA in terms of language support and now they are trying to catch up with SYSCL and SPIR.
- fulafel 10y agoGLSL does have things in common with functional programming. Immutable inputs, restricted rules for mutating data, no side effects.