Linked by Thom Holwerda on Fri 14th Dec 2012 11:51 UTC
Thread beginning with comment 545424
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2005-11-29
Ok, some WebGL is constantly changing and you want Microsoft to implement it NOW? How about finish it first, take it to the appropriate standards bodies, and then come back?
These things should be debated in the open, and I'm sure there are more than a fair amount of people who think WebGL is a laughably bad idea. It's a ridiculous shim between JS and OpenGL which should never exist.
Especially, if, as you said, it destroys battery life. So no, WebGL isn't enabled on iOS. You're just making shit up, AGAIN.
The point is, its there and constantly improving. In Firefox, in Opera, in Safari, in Chrome. They all work on it, make it better, make it great and once the Tim is come (and I am sure that is ore winner then later) it I'll be enabled as default.
So it's not enabled by default. Okay. No need for a long paragraph, just say its not enabled by default, and don't try to argue with me as if I was wrong before. You were wrong, you misled, and you got caught. AGAIN.
But the IE team does not do anything like that. They not even work on it, push it to the public (disabled as default too) so public CAN TEST, give feedback and help to make there implementation fast, per formant and compatible.
Microsoft does not generally implement "standards" that are in a state of flux. Internet Explorer releases come with an implicit guarantee of support for years to come. It isn't like Firefox 87 or Chrome 215.
Microsoft just ignores it. Rejects it. Case of political reasons since WebGL does not fit into there ActiveX/DirectX vendor lock in strategy. No, its a danger even to enable interoperability.
And DirectX does not fit into Khrono's OpenGL strategy. Its two sides to one coin.
Why don't browser vendors implement XAML? An ISO standard for application markup? Why do they continue to put resources into HTML5?
Because it runs contrary to their core position as a technology. What you're asking for is unreasonable. I'm sure that Microsoft would love an immediate API for the Web, but it will never, EVER be OpenGL.
Make it platform agnostic and you may have something that Microsoft can accept. And if people don't do it soon, they risk Microsoft doing it their own way, submitting it to a standards body, and doing an end run around WebGL. And it'll be all Khrono's fault.
You and people who believe that WebGL should be everywhere have, or are destroying any possibility of an interoperable API for 3D on the web by refusing to play ball with the biggest player in the room.
Its the same Microsoft certified creates own standards to not be compatible with open standards story we saw and still see for decades.
If Microsoft creates their own standards, test suites, and submits them to a standards body, there is NOTHING wrong with that. Just because they don't cherry pick YOUR standards, doesn't mean they're not still open.
You're being ridiculous.
After all this years, after multiple anti-trust cases and official public law-punishment cause of that strategy you not really like to argue against that. Or do you? Is your point that all the judges, the law and the antitrust cases are wrong?
I keep re-reading this thicket of bullshit, but I can't find sense of any of it.