5 ms·
Key questions: 1. Is it open and cross platform? 2. Is it going to be supported across all GPU vendors? If either of those is no, than it's a failure from th
by shmerl 12y ago
Key questions:
1. Is it open and cross platform?
2. Is it going to be supported across all GPU vendors?
If either of those is no, than it's a failure from the start and just another walled garden thing.
- jkrems 12y agoThe whole point is to be closer to the "metal". Doing that across GPU vendors would be, well, OpenGL. It's the same as the native interfaces for the PS4 and other consoles - it's supposed to be platform/GPU specific. There's a limit to how much performance a general purpose graphics abstraction can enable.
- foxhill 12y ago> There's a limit to how much performance a general purpose graphics abstraction can enable. that remains to be seen, especially given how similar all the GPUs are today. if it weren't for the longs peak shambles, we might not need Mantle/Metal.
- MaxBarraclough 12y ago> if it weren't for the longs peak shambles, we might not need Mantle/Metal. Given than Mantle is being used in AMD/Windows (in preference to Direct3D - no OpenGL to be seen) it doesn't seem fair to blame only OpenGL.
- foxhill 12y agoDirectX has it's own problems.
- toksaitov 12y agoI think we all know the answers from day 1
- to3m 12y agoBeing "another walled garden thing" will hardly be its death knell. Proprietary single-vendor APIs are already common on games consoles, and it hardly seems to have caused a problem. Look at DirectX, even; not quite single-GPU-vendor, but hardly renowned for its portability, and popular nonetheless. These things will succeed if the platform is popular, and other factors are pretty irrelevant. I suspect iOS is popular enough to make this work.
- shmerl 12y agoI don't mean it won't be used. You are right, for example PS4 uses its own PSSL. But it's still a failure, because it's bad for developers who have to support multiple APIs and bad for users who likely won't get some titles for their platform because developers have no resources to support multiple APIs.
- MBCook 12y ago> But it's still a failure, because it's bad for developers who have to support multiple APIs and bad for users who likely won't get some titles for their platform because developers have no resources to support multiple APIs. That doesn't make it a failure, that makes it something you don't like. This could easily be very big. If it helps developers make faster/better looking games on iOS they'll do it, especially if it's supported by middlware (since most devs probably don't make their own engine). It that happens to make it harder to port games to Android (or at least get them to look as good), so much the better for Apple.
- shmerl 12y agoI don't like it for a reason that it multiplies exclusive titles. I consider it a failure. Normally authors should aim to reach the most audience, not to exclude users because they use a different OS. This API will proliferate the later.
- MaxBarraclough 12y agoA failure is something which doesn't succeed in achieving its goals. We often approximate this by looking at how widely used something is. For an API, this measure seems reasonable. It has nothing to do with your views on vendor lock-in. Direct3D also causes lock-in. That doesn't make it a failure.
- chrisdevereux 12y agoFor many developers, the cross-platform API that they care about is Unity or some equivalent. They will continue to be cross-platform and get a free speedup from the removal of an unnecessary layer of abstraction.
- shmerl 12y agoBut not for all. I'm talking about original engine developers here.
- cwp 12y agoNo and no. But that doesn't mean it'll be a failure. People who write games for iOS are going to love it.
- shmerl 12y agoSo more exclusive titles to expect. Nothing good in it.