4 ms·

They say they are not making an AAA engine. They are looking for a simple way to get into graphics. They have no need for parallel, low-level APIs.

gpm 6y ago
> Please don't comment about the voting on comments. It never does any good, and it makes boring reading. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html In this case specifically I'd just use the second half of your comment, the first half just detracts from the message and sounds petty.
- jfkebwjsbx 6y ago
  I edited it, but let me say I don't agree with your policy, because downvoting is reserved for high-score accounts. If it would be open to (almost) everyone, then it would be fine. In fact, if you think about it, what is "petty" isn't talking about downvoting, but the ability to downvote itself. Flagging is fine, because trolls will always be around.
pjmlp 6y ago
Except going forward, those are going to be the only APIs available, regardless of one is doing AAA or not. It would be the same as using SVAlib or Allegro nowadays. They are still there, but not longer map to existing graphics hardware.
- jfkebwjsbx 6y ago
  > Except going forward, those are going to be the only APIs available That is false. There are already library implementations of legacy OpenGL, modern OpenGL, OpenGL ES, WebGL, legacy Direct3D, Direct3D 10/11, Direct3D 12, Vulkan and others. Major players like Microsoft, AMD, Khronos, Valve and others already depend and employ people on providing those APIs and libraries long-term. Those APIs are not going anywhere, even if a hardware vendor decides to only provide a low-level one (which is understandable, by the way...). > They are still there, but not longer map to existing graphics hardware. They have never mapped to hardware, so there is no real difference between now and then.
  - pjmlp 6y ago
    Those wrapper libraries are yet another layer to debug and not 100% the real deal, and will get further away as the underlying technology evolves. That is like telling someone that coding against POSIX.1 is all they will ever need for their applications.

gpm 6y ago

> Please don't comment about the voting on comments. It never does any good, and it makes boring reading. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html In this case specifically I'd just use the second half of your comment, the first half just detracts from the message and sounds petty.

jfkebwjsbx 6y ago
I edited it, but let me say I don't agree with your policy, because downvoting is reserved for high-score accounts. If it would be open to (almost) everyone, then it would be fine. In fact, if you think about it, what is "petty" isn't talking about downvoting, but the ability to downvote itself. Flagging is fine, because trolls will always be around.

pjmlp 6y ago

Except going forward, those are going to be the only APIs available, regardless of one is doing AAA or not. It would be the same as using SVAlib or Allegro nowadays. They are still there, but not longer map to existing graphics hardware.

jfkebwjsbx 6y ago
> Except going forward, those are going to be the only APIs available That is false. There are already library implementations of legacy OpenGL, modern OpenGL, OpenGL ES, WebGL, legacy Direct3D, Direct3D 10/11, Direct3D 12, Vulkan and others. Major players like Microsoft, AMD, Khronos, Valve and others already depend and employ people on providing those APIs and libraries long-term. Those APIs are not going anywhere, even if a hardware vendor decides to only provide a low-level one (which is understandable, by the way...). > They are still there, but not longer map to existing graphics hardware. They have never mapped to hardware, so there is no real difference between now and then.
- pjmlp 6y ago
  Those wrapper libraries are yet another layer to debug and not 100% the real deal, and will get further away as the underlying technology evolves. That is like telling someone that coding against POSIX.1 is all they will ever need for their applications.