[deleted]
Google nabs Square Enix and other game developers for native client Chrome games
11–20 of 47 posts
Re: Google nabs Square Enix and other game developers for native client Chrome games
#12There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
The major difference being that Microsoft has a history of anticompetitive behavior and google does not. Your unfounded wharrgarble is noted, though.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#13There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
NaCl uses the NPAPI which is pretty standard, it's used for flash for example and is supported by Firefox, Opera and webkit. This means NaCl could be plugged in those browsers without being reimplemented.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#14There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
NaCl uses the NPAPI which is pretty standard, it's used for flash for example and is supported by Firefox, Opera and webkit. This means NaCl could be plugged in those browsers without being reimplemented.
"Could be".
Will not be unless they have no choice to survive. Google knows that, everyone knows that.
Not a web standard.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#15There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
NaCl uses the NPAPI which is pretty standard, it's used for flash for example and is supported by Firefox, Opera and webkit. This means NaCl could be plugged in those browsers without being reimplemented.
For now, that is true. However, NaCl is moving to the Pepper API, which is a proprietary Chrome API for plugins.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#16There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
The major difference being that Microsoft has a history of anticompetitive behavior and google does not. Your unfounded wharrgarble is noted, though.
Google is very similar.
They do open up a lot of stuff, and provide a lot of free stuff too. They have a lot of talented people as well.
But their base strategy is to control our most powerful tool. For that you need to kill standards. And hey, talented people sure know how to put things on the right balance, at the right time.
I'm not sure who you think can compete with Google. For most people "the internet" is Google.com.
Google.com tells you to get Chrome.
Most top 10 downloaded software bundle Chrome, often with default optin and even default launch.
Companies which aren't big enough to fight are bought out.
See a trend?
What's funny is that my comment gets back to 0 or 1 then back to minus and so on.
What it shows is that this is controversial and many actually agree with my "wharrgarble". Maybe you should give it a deeper though. We'd be better in 5 years from now, if everyone though about such things with a little more criticism.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#17Earlier quoted context omitted.
Bastion runs on Mono, and Mono runs on native client (including the JIT, which required some special work in native client itself). Actually all three apps they demo'd running on native client were also running on Mono!
Do you know what the solution was for XNA? The last time I checked, all the Mono XNA ports were in miserable shape. Considering Bastion makes use of shaders and mixed mode 2d/3d rendering, it seems like it must be running on a high quality port of a large portion of the XNA stack.
Replying to provide follow-up detail: I dug into the executables and it looks like it uses OpenTK for rendering and FMod to sound, instead of using a port of XNA. Both are freely available, so that's a pretty simple path to doing a similar port for other XNA games. Neat.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#18There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
The major difference being that Microsoft has a history of anticompetitive behavior and google does not. Your unfounded wharrgarble is noted, though.
You'd think it would be good to see the problems this will unleash on openness before it's too late and we have to say 2 years down the road, on the next embrace-extend move, that Google has a history of this.
Google is using their muscle to push for the adoption of a Google-exclusive technology in browsers that Google's competitors have said they cannot support because it is not truly open. If you can't see that this is embrace, extend & extinguish in action, then you're either naive or your memory is too short.
Re: Google nabs Square Enix and other game developers for native client Chrome games
#19There you go: Google's embrace, extend, extinguish. Just like MS, but with better cover. "Its open!" Of course, no one else will implement.
NaCl uses the NPAPI which is pretty standard, it's used for flash for example and is supported by Firefox, Opera and webkit. This means NaCl could be plugged in those browsers without being reimplemented.
So, it's about as open as Flash, which is a free standard we're all happy about.
No, wait...
Re: Google nabs Square Enix and other game developers for native client Chrome games
#20Earlier quoted context omitted.
NaCl uses the NPAPI which is pretty standard, it's used for flash for example and is supported by Firefox, Opera and webkit. This means NaCl could be plugged in those browsers without being reimplemented.
For now, that is true. However, NaCl is moving to the Pepper API, which is a proprietary Chrome API for plugins.
> proprietary Chrome API
You keep using that word. I do not think it means what you think it means. From Wikipedia:
"""Proprietary software is computer software licensed under exclusive legal right of the copyright holder. The licensee is given the right to use the software under certain conditions, while restricted from other uses, such as modification, further distribution, or reverse engineering."""
Nothing of this applies to Pepper API or NaCl. Mozilla can implement Pepper API and NaCl or can even just take NaCl as whole because it is, oh boy, oh boy, open source with a permissive license.