Apple Seeks To Position Metal as Part of New 3D Graphics Standard For Web (appleinsider.com) 170
Mikey Campbell, writing for AppleInsider: Apple's WebKit team on Tuesday proposed a new Community Group at the World Wide Web Consortium (W3C) that will focus on developing a new standard API, perhaps based on Metal, for accelerating GPU-based 3D graphics and general computation for the web. Announced through Apple's WebKit blog, the new 'GPU for the Web' Community Group will discuss a potential next-generation web graphics API that can better leverage modern GPUs. Along with 3D content, Apple proposes GPU architecture might also be used to accelerate general web computations. As noted by Dean Jackson from the WebKit team, advancements in the GPU hardware space has led to identical enhancements in software APIs. He cites platform technologies like Apple's Metal, Microsoft's Direct3D 12 and the Khronos Group's Vulkan as offering lower overhead, and thus better performance, than the OpenGL standard. Unfortunately, the new graphics APIs contain nuanced architectural differences and are not available across all platforms, making them unsuitable for wide implementation on the web.
Vulkan (Score:5, Insightful)
The whole point of Vulkan is that it is a modern, high-performance, platform-agnostic API. Isn't that what they should use? It's already positioned as all that, it just needs the web folks to adopt it.
Re:Vulkan (Score:5, Insightful)
Re: (Score:2)
Ummm... buy out MS?
Re: (Score:3)
Re: (Score:2)
Maybe Apple, Google, Amazon and Disney could all team up and absorb it.
Re: (Score:2)
Speaking of, what the hell is with Apple fans throwing around APPLE COULD BUY YOO at everything?
Even if Apple did have the resources on hand to purchase the entire market capitalization of Microsoft, what the hell makes anyone think the MS shareholders would jump at the opportunity of a one-time-buyout of their ownership of one of the largest tech companies in existence?
Re: (Score:2)
Re: (Score:2)
Yeah, you'd laugh... right up until the point where you realize that you've now got a far more powerful and abusive monopoly than you EVER had with MS.
Does the term "cut off your nose to spite your face" ring a bell? 'Cause that's what that would be, big-time.
Re: (Score:2)
And when exactly has MS ever innovated?
Re: (Score:3)
That 640 KiB limit was pretty innovative and it required courage.
Re: (Score:2)
I thought that was Intel's thing?
Re: (Score:2)
I think it was IBM's thing. PC/XT, PC/AT, etc.
Re: (Score:2)
The original PC processor could only address 1MB of Ram. The first 640K was reserved for applications and the rest used by the system. MS-DOS was designed for this and when the 286 which could address 16MB came available they had to work around the limitations of MS-DOS. I never dealt with it as I went from the C64 to Amiga systems which ran off Motorola processors which were vastly different. My first PC was a dual PII 333 server that I installed SUSE linux on in 1999. Once I got used to using Linux I
Re: (Score:2)
And when exactly has MS ever innovated?
Software licensing. They may not have invented licensing but they took it to a whole other level. For a while they were actually getting away with forcing enterprises to pay a seat license for every desktop in the office. That Sun Sparc-Windows license. That Mac-Windows license. That Silicon Graphics Iris-Windows license.
Re: (Score:2)
And when exactly has MS ever innovated?
Microsoft Surface Pro... You can argue that it's just another tablet computer but they finally got it right and it's one of the best Windows tablets you can buy.
Microsoft Mouse... Still a decent mouse
Microsoft Word, Exchange, Outlook, etc... Exchange and Outlook were innovative for their time and were a part of the shift towards the digital office.
I'm sure that there are more on the programming side, etc., but these are the ones that most would be familiar with.
Re: (Score:2)
Re: (Score:2)
Re: (Score:3)
But then how can Apple gain a proprietary stranglehold on the industry? How can they force adoption of their own standard and ensure a way to monetize all future 3D web graphics?
Considering the history of Apple open source contributions in things like OpenGL, I'd say your concerns are at best not really likely. Also Apple is proposing a new standard which means it will be a standard unlike MS and the embrace and extend philosophy.
Re: (Score:3)
But then how can Apple gain a proprietary stranglehold on the industry? How can they force adoption of their own standard and ensure a way to monetize all future 3D web graphics?
Considering the history of Apple open source contributions in things like OpenGL, I'd say your concerns are at best not really likely. Also Apple is proposing a new standard which means it will be a standard unlike MS and the embrace and extend philosophy.
Exactly. Apple has a pretty good track record of leaving things Open. Take CUPS for example.
Re: (Score:2)
Like they were going to opensource their video chat software. Oh, some small puny company sued and now we can't even though we could buy out the company 1000 times over.
False equivalence. Because Apple has not open-sourced all their software, that doesn't mean they don't open source some of their software.
As for CUPS, can you tell me what they added?
If only CUPS was open source software where you could look at the changes [github.com] from when Apple bought cups to what the latest version [github.com]. I'll give you a hint, click on the text files that are named "CHANGES".
The only thing that I see they added on a cursory search is their own services for "zero configuration"... and even then, I'm not even sure those are open source.
Then you would be wrong. ZeroConf [zeroconf.org] is the open source implementation of what Apple started as Bonjour/Rendevous.
It requires paid lilcensing to use in a commercial setting. HMM... I wonder why they contributed?
I don't know what you are talking about. I've paid $0 for mor
Re: (Score:2)
That example was not 'all their software.' It was a piece of software they promised to open and reneged on. A piece of software that would open their userbase up to videoconference to their friends who they then wouldn't have to urge to buy an iPad.
Re: (Score:2)
That example was not 'all their software.' It was a piece of software they promised to open and reneged on. A piece of software that would open their userbase up to videoconference to their friends who they then wouldn't have to urge to buy an iPad.
So Apple "promised" to open source FaceTime but didn't. Apple as a company can't be allowed to make decisions on their own software?
Re: (Score:2)
Re: (Score:2)
Apple may have made many open source contributions to OpenGL over the years but they've never bothered implementing anything better than OpenGL 4.1 on their own systems, even though the same graphics chips they use have OpenGL 4.4 and 4.5 implementations on other platforms.
IMO their OpenGL implementations also seem quite flakey, e.g.: half the time VirtualBox guests only draw
Re: (Score:2)
Apple may have made many open source contributions to OpenGL over the years but they've never bothered implementing anything better than OpenGL 4.1 on their own systems, even though the same graphics chips they use have OpenGL 4.4 and 4.5 implementations on other platforms.
True Apple hasn't kept up with OpenGL as much as some people would have liked; however, is there are a technical reason (like going with their own platform) behind the lack of support? Considering that Apple contributed to OpenGL since 1.0, I would say it's not because of a philosophical aversion to it but maybe technical and practical concerns.
Re: (Score:2)
Apple abandoned that long ago and have been lagging years behind in OpenGL support in favor of their proprietary Metal API even years before Metal was even available. Even their latest Sierra only offers a maximum of 4.1 (released 7 years ago) with some 4.2 extensions. Instead of contributing to Vulkan (OpenGL Next) they decided to go proprietary instead and then have this to say:
OpenGL is one of many open source projects Apple has supported. As a company, Apple abandoned it when they decided to go in another direction and with their own platform.
Guess which platforms Vulkan isn't available on? Oh of course, Apple's platforms!
Then you would be wrong [moltengl.com].
Apple's support for standards goes right up until they can capitalize it for vendor lockin, AirPlay, Lightning, Facetime, Airdrop, etc.
When was AirPlay open source again? Never.
When was Lightning open source again? Never
Airdrop, etc?
Your complaint that Apple doesn't open source everything is negated by the open source Apple has been known to work on: OpenCL, ZeroConf, Clang/LLVM, WebKit, CUPS, etc.
Re: (Score:2)
Apple will opensource software technology that doesn't threaten their ability to engage in vendor lock-in.
It's not more complicated than that.
Re: (Score:2)
Re: (Score:2)
They didn't open source CUPS; they simply didn't close it after they bought it.
Re: (Score:2)
Re: (Score:2)
ZeroConf could do that but they open-sourced that.
Wrong. Apple did not open source ZeroConf, it is apparent you do not know what ZeroConf is.
CUPS could have done that. But that open-sourced that.
Wrong again. Apple did not open source CUPS.
Re: (Score:2)
Wrong. Apple did not open source ZeroConf, it is apparent you do not know what ZeroConf is.
I remember it this way:
Apple releases Bonjour (then known as Rendezvous) [apple.com] in 2002 under the Apple Public Licenses which is considered open source.
Based on Bonjour, Avahi [wikipedia.org] was created in 2004 because the APL was not GPL compatible.
The Avahi project started in 2004 because Apple's Zeroconf implementation, Bonjour, used the GPL-incompatible Apple Public Source License. In 2006 Apple relicensed parts of Bonjour under the Apache License. However, Avahi had already become the de facto standard implementation of mDNS/DNS-SD on free-software operating systems such as Linux.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Bonjour is Apple's version of ZeroConf which they open sourced before Avahi was a project in Linux.
I know what Bonjour is, I'm wondering why you said they open sourced ZeroConf, which is a specification that has a variety of implementations. In any case I think this is going off topic, the point is when it comes to 3D graphics Apple's history is extremely poor support of OpenGL, no support for Vulkan at all and ultimately going a proprietary API despite being a promoter member of the Khronos group.
Re: (Score:2)
Wrong again. Apple did not open source CUPS.
And all these years that Apple has kept this project open source does not count?
Re: (Score:2)
"OpenGL" is not open source,
You would be wrong [sgi.com].
That is a layer on top of Metal that translates calls from one API to another, it is not Vulkan on macOS or iOS because those platforms do not support it as Apple quite rightly stated. You are arguing against facts by providing evidence you clearly have absolutely no understanding of whatsoever.
So you're saying it's not "available" because it doesn't fit your definition of "available". Can you get Vulkan on macOS? Yes. Is it officially supported by Apple? No.
Re: (Score:2)
No I am not wrong, you simply misunderstand.
From the page again:
"The following are the currently available licenses:
Open source license - for use of the S.I. This is a Free Software License B closely modeled on BSD, X, and Mozilla licenses.
Trademark License - for new licensees who want to use the OpenGL trademark and logo and claim conformance."
It says it in black and white: OPEN SOURCE LICENSE.
To help you along just try and show me Apple's open source OpenGL implementation. Oh you cant do that? Im not surprised, because it is not open source.
Please read what I wrote above: "OpenGL is one of many open source projects Apple has supported. As a company, Apple abandoned it when they decided to go
Re: (Score:3)
It looks like Rambus all over again. Proprietary components should not be part of standards, period.
Re: (Score:3)
Please elaborate on what you mean by "proprietary". Metal is competing with Vulkan and Direct3D as the successor to OpenGL. Apple wants the next version to be based on their work on Metal. Such version will undoubtedly be open source unlike Direct3D and WebGPU will is proposed to replace OpenGL.
To help get things started, Apple's WebKit team is proposing an initial API dubbed "WebGPU." Apple began testing next-generation APIs in WebKit "a few years ago" and found encouraging results, so the company is sharing its WebGPU prototype with the the W3C Community Group.
Re: (Score:2)
Metal is competing with Vulkan and Direct3D as the successor to OpenGL.
Absolute rubbish. Direct3D is Microsoft's attempt to exterminate OpenGL, not succeed it. Metal is Apple's attempt to undermine Vulkan, for no good technical reason. Both are fighting a losing position, sorry about your narrative.
Re: (Score:2)
Absolute rubbish. Direct3D is Microsoft's attempt to exterminate OpenGL, not succeed it. Metal is Apple's attempt to undermine Vulkan, for no good technical reason. Both are fighting a losing position, sorry about your narrative.
Between MS and Apple which company has advanced open source more. You think that because Apple doesn't want to use Vulkan that must mean they have no good technical reason. Look at what Apple did with Clang/LLVM. gcc is a good compiler but Apple could not get the optimization they wanted from the gcc moderators. So they backed Clang/LLVM instead. Now there are two decent open source compilers you could use. If you want to plug your laptop into a dock in the future, it looks like the way to do it is not with
Re: (Score:2)
You think that because Apple doesn't want to use Vulkan that must mean they have no good technical reason.
Thanks for telling me what I think, it makes you sound very "Apple". No. I said that Apple has no good technical reason for undermining Vulkan. Would you please refrain from twisting my words, or should I just accept that you are too "Apple" to care about that.
Re: (Score:2)
Thanks for telling me what I think, it makes you sound very "Apple". No. I said that Apple has no good technical reason for undermining Vulkan.
And how would you know that? Do you work for Apple? The problem you have is that you have the burden of proving Apple has "no good technical reason." This is my understanding of the problem: Metal released with iOS 8 [wikipedia.org] in September 2014. Later it was added to macOS El Capitan. Vulkan's [wikipedia.org] initial release is Feb 2016. Somehow I think time travel is beyond Apple's capabilities especially since PowerVR didn't support Vulkan until March 2016 (which Apple uses for their mobile GPU). So the most basic technical reaso
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
People, people. There's no need to fight. We can't pick Vulkan even if we wanted to. Don't you remember it's going to be destroyed on stardate 2258.42?
Re: (Score:2)
"Our Metal(*patent pending) API brings you closer to metal. Our API is better in every way. The whole industry is using Metal to drive metal!"
Re: (Score:2)
A better start would be to change the name entirely because MeTaL for graphics already existed (and is still in use in one of my OLD machines just to demonstrate what a failure it was.) S3 anyone?
Re: (Score:2)
But then how can Apple gain a proprietary stranglehold on the industry? How can they force adoption of their own standard
Yeah, it's a real shame how they used their stranglehold over WebKit to control the direction Chrome is going; LLVM and related technologies (e.g. Clang) to control the direction a huge chunk of the software industry is going; CUPS to control the printer industry...
A real shame.
Not to mention all of the other projects and code they contribute [apple.com] to the open source community.
I agree that Apple does do a lot of proprietary stuff (e.g. connectors, protocols, etc.), but they're used as a means for tying people to
Re: (Score:2)
Re: (Score:2)
Millions of college students in dorm rooms got the RIAA to give up on DRM for music.
Jobs rode along for the credit.
Re: (Score:2)
Jobs rode along for the credit.
From the beginning iPods played DRM free music. The problem was that they could not sell music DRM free from the iTunes store at the insistence of the music companies. Ironically, the music companies in their short-sightedness made Apple's position stronger. In the beginning, the music company thinking was Apple was a small player and surely the PlaysForSure architecture would overtake FairPlay with its larger number of hardware options and outlets. In actuality, the issue was PlaysForSure wasn't as reliabl
Re: (Score:2)
Also, Jobs took up the suggestion he had made to Skully and started selling sugar water to kids, by putting labels for 'free itunes songs' on the bottlecaps of popular brands of soda.
The irony was missed by many.
Re: (Score:2)
If you think Apple is on the evil side, your gauge must have Stalin on the good side. I wouldn't trust your gauge.
Re:Vulkan (Score:5, Insightful)
Apple was a member of Vulkan and those of us who code to GPUs were excited to have a unified target finally coming into view - until Apple withdrew and announced a proprietary alternative. They shouldn't be allowed to influence the standard now.
Re: (Score:2)
Apple was a member of Vulkan and those of us who code to GPUs were excited to have a unified target finally coming into view - until Apple withdrew and announced a proprietary alternative. They shouldn't be allowed to influence the standard now.
They're not "influencing" Vulkan. They are offering their own standard. Just like whenever something gets forked.
Re: (Score:3)
When something gets forked, if the fork sucks, you can fork it again. Think Apple is gonna drop some Metal drivers on my Linux box? No, this is exactly what they are trying to do- erect a toll across the bridge someone else built.
Um if Apple is proposing a new standard, they won't be the ones to do it. It's a standard. Just like Apple has contributed on OpenGL for years. Did they write an OpenGL driver for Linux machines? No. AMD, NVidia and Intel did that.
Re: (Score:2)
They can propose a standard... there is a difference between proposing and declaring.
And what does working within a W3C group fall into the distinction for you? It seems like they are working within a standards body to propose standards.
Anyone can propose a standard, the only nonsensical proposal would be to offer a proprietary piece of technology as a standard which they are not willing to open source (like Microsoft did with DirectX... which the W3C obviously ignored).
Yes which is why they want the W3C to get involved. Also Apple is leveraging their ideas on Metal not necessarily that the new standard is Metal which is a different idea.
Re: (Score:2)
The thing is it is all too easy for a company like Apple to deceptively jump in bed with a huge number of external devs and then turn over and leave with an insane amount of knowledge now headed for the proprietary development of their own system.
Your assertion would be false: Apple announced Metal at WWDC 2014 (June). They even have a video [apple.com] of the presentation. It was released in Sept 2014 for iOS 8.
Vulkan API was not formally announced [phoronix.com] until March 2015. Version 1.0 of the specification would not be released until Feb 2016.
In any way you look at it, Apple released Metal long before the Khronos Group announced Vulkan.
Re: (Score:2)
Company A joins a standards body to try to unify the solution to some problem. That solution gets near, and Company A leaves, then proposes a new standard for everybody, further fragmenting the solution.
I'm all for innovation and standardization, though I much prefer the approach like X windows. "Hey, this is getting old and crusty, we need some answers folks" then a few groups come up with ideas, and gradually we get to a consensus (looking like Wayland). Thi
Re: (Score:2)
You're absolutely right. What we need is a unified view, followed by everyone.
I don't have the technical details for all the platforms, APIs and such, but I already got a few names:
- BorgOS
- BorgHTML
- BorgCSS
- BorgGPU
- BorgAudio
- BorgStreaming
Re: (Score:2)
Re: (Score:2)
1. Do not buy non-free operating systems or software. Instead use Linux or BSD or even GNU Hurd (I recommend Linux).
2. Do not write code for non-free operating systems or software. Instead write code using widely supported standards (i.e. Vulkan) that runs on all platforms (especially freedom-supporting platforms like Linux or BSD). In this case do not ever write code using Metal for any reason under any circumstances. Apple will come around and support Vulkan once they r
Re: (Score:2)
Company A joins a standards body to try to unify the solution to some problem. That solution gets near, and Company A leaves, then proposes a new standard for everybody, further fragmenting the solution.
That isn't the problem in this case. Apple initially joined the Vulkan group in 2014 when it was announced; however by 2015, they had left the group. The Vulkan spec wasn't released until a year later. I would guess that the Vulkan group moved too slowly for Apple.
Re: (Score:2)
Unfortunately, the new graphics APIs contain nuanced architectural differences and are not available across all platforms, making them unsuitable for wide implementation on the web.
You must have missed that part.
Re:Vulkan (Score:5, Informative)
Everyone in the comments suggesting we should just use their favorite graphics API is missing the point entirely.
Neither Vulkan nor its competitors are safe to use with untrusted code from the web. Allowing any random web developer to have access to the full capabilities of any of those APIs is a recipe for disaster. This standard is, from what I can gather, intended to be a layer that abstracts away the underlying API, whether it be Metal, Vulkan, or Direct 3D 12, which should provide a safe means for using them.
For an initial implementation, Apple is providing a prototype that is compatible with Metal, given that they had apparently already done quite a bit of work mapping Metal to Javascript, but it's clear that the end goal with this standard is to provide something that is compatible with all of these close-to-the-metal APIs. I imagine that version 1 of the standard will resemble an intersection of features between the competing APIs, that way they can ensure the broadest compatibility right from the get-go.
In addition to but separate from the web standard, they're talking about taking Metal cross-platform. That wouldn't affect the web standard (which, again, should be able to work on top of any of these competing APIs), but it would ensure that the standard is usable on any platform they choose to support with Metal. If they do take Metal cross-platform, that would seem to suggest an uptick in their interest in creating web-based products that are consistent and in top-shape across a variety of platforms, in much the same way that Google created Chrome to do the same.
Re: (Score:2)
I do not understand the need to try and shove remotely hosted applications into a web browser. WTF people? Do you try to make horses fly or do you just say horses are completely unsuitable for air travel and create a jetliner?
People. Are. Insane.
Re: (Score:2)
The point of Metal, Vulkan and DX12 is that they give a fairly low-level abstraction to the graphics hardware.
No web site should have low-level access to the user's system in any way. That is the big fallacy here.
As to platforms, all Apple iPhones and iPads have come with PowerVR GPUs. PowerVR was an early adopter of Vulkan and one of, if not the first to demo it.
For Apple to adopt Vulkan should not be too difficult for them. Apple only does not want to because they are too invested in Metal.
The best thing about standards is (Score:2)
Headline doesn't really match actual news (Score:5, Informative)
Where in the article does it suggest that Apple is making a power play here to position Metal like the headline says? This really doesn't have a whole lot to do with Metal specifically, and is instead about leveraging the entire class of APIs that have been coming out that are closer to the (lowercase) metal. In fact, they specifically said so in the summary:
As noted by Dean Jackson from the WebKit team, advancements in the GPU hardware space has led to identical enhancements in software APIs. He cites platform technologies like Apple's Metal, Microsoft's Direct3D 12 and the Khronos Group's Vulkan as offering lower overhead, and thus better performance, than the OpenGL standard.
The only thing special about Metal that's mentioned in the article is its role in the initial implementation. To pull the relevant quote:
While Metal appears to underpin Apple's initial web graphics proposal, the company does not expect its concept to become the ultimate standard. That said, it appears Apple is angling to take Metal cross-platform.
"We don't expect this to become the actual API that ends up in the standard, and maybe not even the one that the Community Group decides to start with, but we think there is a lot of value in working code," Jackson says.
So, basically, Apple folks have access to Metal and understand how it works, so they're starting with what they know and have so that they can get the ball rolling quickly. Where it goes from there is up to the community, which, given Apple's typical approach their open source/community-driven projects (e.g. WebKit, LLVM, Clang, Swift, etc.), it's likely that they actually mean that. Of course, they'll no doubt use their role in the community to try and steer things to their own advantage, but if they do so too much it's likely that this will simply become another dead-end "standard" that no one adopts.
Re: (Score:2)
Where in the article does it suggest that Apple is making a power play here to position Metal like the headline says? This really doesn't have a whole lot to do with Metal specifically, and is instead about leveraging the entire class of APIs that have been coming out that are closer to the (lowercase) metal. In fact, they specifically said so in the summary:
No way is Apple making this power play.
If they did then they'd take 3d graphics hardware more seriously. As it is Apples graphics offerings are a joke, both literally and figuratively.
Re: (Score:2)
If they did then they'd take 3d graphics hardware [on desktops] more seriously. As it is Apples graphics offerings are a joke [to me], both literally and figuratively.
I think a problem here is everyone is only thinking about the PC. 3D and web content acceleration is something that affects mobile as well. Apple is looking for something that works for both their mobile GPUs as well as desktop ones. Currently Vulkan is an option however it is relatively new.
Re: (Score:2)
Where in the article does it suggest that Apple is making a power play here to position Metal like the headline says? This really doesn't have a whole lot to do with Metal specifically, and is instead about leveraging the entire class of APIs that have been coming out that are closer to the (lowercase) metal. In fact, they specifically said so in the summary:
No way is Apple making this power play.
If they did then they'd take 3d graphics hardware more seriously. As it is Apples graphics offerings are a joke, both literally and figuratively.
Then why do you sound so nervous?
Re: (Score:2)
Where in the article does it suggest that Apple is making a power play here to position Metal like the headline says? This really doesn't have a whole lot to do with Metal specifically, and is instead about leveraging the entire class of APIs that have been coming out that are closer to the (lowercase) metal. In fact, they specifically said so in the summary:
No way is Apple making this power play.
If they did then they'd take 3d graphics hardware more seriously. As it is Apples graphics offerings are a joke, both literally and figuratively.
Then why do you sound so nervous?
Because I know that my non-adoring comments on Apple products are going to be modded into oblivion.
Re: (Score:2)
Because I know that my idiotic comments on Apple products are going to be rightfully modded into oblivion.
Fixed that for you.
Thanks because as a fanboi you are totally in your right to correct my erroneous and heretical comments.
Re: (Score:2)
Apple has the best graphics on mobile by a wide margin. The desktop no but on mobile they are killing it.
Re: (Score:2)
Re: (Score:3)
Re: (Score:2)
I'm simply pointing out that Apple don't really care for open standards. If they did they'd implement Vulkan.
And if they don't like a standard, the direction, or the process it takes to change something, you're still arguing that they should implement a standard they don't like? That seems counter to open source. Could Apple fall flat on their faces for implementing a new standard? Yes. That doesn't mean they should always just follow what others do.
For example, everyone in open source used gcc as the compiler for years. So did Apple; however, they found they got less than stellar support when trying to get change
Re: Headline doesn't really match actual news (Score:2)
Protip:
Open source and standard are two very different things.
There is not even that much overlap.
You are confusing the two.
Some standards do not even allow an open source implementation (sure to associated patent coverage).
Most open source in no way represent a standard.
They. Are. Two. Different. Concepts.
Please stop trying to treat them as the same thing. It's is stupid.
Re: (Score:2)
Has Apple backed open standards? Yes, they've even created some. Have they backed open source? Yes. The original poster is somehow ignoring that while Apple does back proprietary things, they also back open standards and open source.
Re: (Score:2)
I'm simply pointing out that Apple don't really care for open standards. If they did they'd implement Vulkan.
As I've already pointed out elsewhere in response to you [slashdot.org], you seem to be very confused about what all of this means. You're basically suggesting Apple doesn't care about open standards because they're making a car (a safe abstraction for the graphics/compute layer) instead of implementing a gasoline engine (the unsafe graphics/compute layer). Never mind that they intend to use the gas engine--as well as other engines--in their car.
Re:Headline doesn't really match actual news (Score:5, Informative)
You clearly have no idea what any of this is about, because what you just said is a terrible idea regardless of whether you support Vulkan or not.
For one, Vulkan and its competitors aren't designed for use with untrusted code, so there are quite a number of significant security and technical concerns with your notion that we can simply adopt one of them as a web standard that any random web developer has full access to (which would've been just as true had you said Metal or Direct 3D 12 instead). What you "need", then, is a safe layer that abstracts the underlying API and provides safety to the user (I say "need" in quotes, because I'm not actually clear that this is something we want, let alone need).
Second, neither Vulkan nor its competitors are actually cross-platform in practice today. It may be the case that one of them will become more widespread over time, but, for now, the world we live in is a fragmented one. Any given platform likely supports at least one of these competing standards, but you can't count on having support for any particular one. A web standard that lives over all of them would make it possible to tap into that power without having to know anything about any of them.
When they talk about using Metal for this standard's initial implementation, what they mean is that they've already done most of the work of mapping Metal back to existing web standards (e.g. Javascript), so they have a head start on which features a standard may be able to support and what that web API may look like. They'll likely take something resembling the intersection of Metal's features with Direct 3D 12's and Vulkan's features so as to provide an initial release of the standard that works across most platforms.
When they talk about Metal going cross-platform, that's a separate (but related) topic. It wouldn't affect this standard (i.e. you should eventually be able to use this standard with Metal as easily as with Vulkan), but it would provide them with a means for ensuring the availability of the standard across any platforms supported by Metal.
Re: (Score:2)
For one, Vulkan and its competitors aren't designed for use with untrusted code, so there are quite a number of significant security and technical concerns with your notion that we can simply adopt one of them as a web standard that any random web developer has full access to (which would've been just as true had you said Metal or Direct 3D 12 instead). What you "need", then, is a safe layer that abstracts the underlying API and provides safety to the user (I say "need" in quotes, because I'm not actually clear that this is something we want, let alone need).
I would hope they already offer some protection against one malicious or malfunctioning process crashing or snooping on other processes or hogging all the resources, I'm sure you need some kind of sandbox but creating a whole new API for that seems like major overkill. You got JS in the browser, Node.JS on the server. Java applets in the browser, Java on the server. If you need a whole new API something's very wrong.
Second, neither Vulkan nor its competitors are actually cross-platform in practice today. It may be the case that one of them will become more widespread over time, but, for now, the world we live in is a fragmented one. Any given platform likely supports at least one of these competing standards, but you can't count on having support for any particular one. A web standard that lives over all of them would make it possible to tap into that power without having to know anything about any of them.
The DirectX/OpenGL divide is ancient, AMD's Mantle API mostly got rolled into Vulkan so Appl
Re: (Score:3)
> For one, Vulkan and its competitors aren't designed for use with untrusted code,
[[Citation]]
Do you have an _actual example_ that shows this or are you just repeating dogma that everyone else does?
> neither Vulkan nor its competitors are actually cross-platform in practice today.
Um, Hello, McFly. We already have WebGL. Hell, even Microsoft supports it on Edge! Of all the graphics API available WebGL is the most cross-platform. The only exceptions that I'm aware of are consoles such as PS3/PS4 and Xb
Re: (Score:2)
> For one, Vulkan and its competitors aren't designed for use with untrusted code,
[[Citation]]
Do you have an _actual example_ that shows this or are you just repeating dogma that everyone else does?
Do you have an _actual example_ that shows there is not an invisible, intangible unicorn standing next to you right now, or are you just repeating dogma that everyone else does?
Repeat after me: you can't prove nonexistence, which is why the onus is on the side claiming existence. If you want to claim that they designed it that way, the onus is on you to prove it. Have fun.
Moreover, what does the cross-platform capabilities of WebGL have to do with my statements regarding Vulkan? Yes, WebGL is cross-platform
Re: (Score:2)
> which is why the onus is on the side claiming existence.
Uhm, Hello, McFly. You are the one making this claim:
1. Where, specifically are the security issues with untrusted code using Vulkan or WebGL ???
2. How is Apple's Metal any better?
Re: (Score:2)
I never said Metal was better. Just because I disagree with what I think is a bad argument coming from you, it doesn't mean I'd support the same bad argument coming from someone on the other side. I honestly don't care which "wins" between Metal and Vulkan.
I never said WebGL was unsafe to use. I was confused why you even brought it up, and still am. It's safe to use and it was designed for the web, but it doesn't provide the close-to-the-metal access this new standard is designed to provide, so it's irrelev
Re: (Score:2)
Re: (Score:2)
Hi Ash-Fox,
I never implied, nor said, nor would say said that Metal is designed to deal with untrusted code. In fact, I never asserted in any of my posts that Metal was in any way superior in any regard whatsoever to the other, competing APIs, nor would I. I merely criticized some overstated headlines and then some poor arguments that would have been just as poor had they come from a Metal or Direct 3D 12 supporter. They just happened to come from someone supporting Vulkan.
Understandably, I won't be replyin
927 (Score:3)
Good. (Score:2)
Where does this fit in Apple's global strategy? (Score:2)
Re: (Score:2)
I'm all for making the web browser more powerful platforms since that can help us be more independent of any concrete OS but I can't understand why Apple does something like this. I mean, they're one of the companies more intently trying to lock everyone in to their platforms. How does this "open" initiative fit with that?
Apple uses lots of open source software. They've championed lots of open source software. This would be no different. One possible advantage is that with everyone using this new standard, Apple isn't locked to a GPU on any platform. Also for them, programming is more simplified Currently they use PowerVR for their mobile and Intel/AMD/NVidia for computers.
Re: (Score:2)
Apple now thinks a fast 3d layer for their content will be useful. Just like Microsoft wanted in the mid to late 1990's.
A fast 3d Web was always a hardware and software dream to different OS teams. A feeling by OS creators that only their OS could bring a gpu and 3d web GUI code together for users and content creators.
That browser developers needed help to fully use all the gpu or cpu with a gpu on modern computers. Only t
Obligatory XKCD (Score:2)
https://xkcd.com/927/ [xkcd.com]
Re: (Score:2)
And since we're going with emulation of the fastest possible CPU and GPU, there's no need to use quad-core multi-GHz intel processors and nVidia graphic chips anymore. That means we can run all our computers and smartphones on something like an Atmel ATmega328p!
Re: (Score:2)
There we go again, someone who doesn't understand why "prefixed stuff" exists in the first place. It's not Apple's fault that people only used their prefixes. You also can't blame them for not removing said prefixes when they add non-prefixed stuff so that old code doesn't suddenly break for no apparent reason.
Blame Firefox and Opera for implementing -webkit-stuff instead.
Re: (Score:2)
You mean the two technologies that don't even exist on some platforms? I'm glad I don't have to deal with your bullshit.