Chrome World Wide Maze
91–100 of 124 posts
Re: Chrome World Wide Maze
#92Earlier quoted context omitted.
No, it's not a perfect game controller. A convenient one maybe, but not perfect, not even good. It has the same problem that you would encounter if you tried touch typing on an iphone keyboard. It has no physical feedback so you have no idea if you are pressing the correct button (or any button at all) on the phone screen unless you are actually looking at it. Which means you won't be able to look at the TV screen at…
Don't you think the reality is some middle ground? It's a perfect game controller for some games .
Re: Chrome World Wide Maze
#93Earlier quoted context omitted.
It's an "experiment", which means it could be using some of the latest and cutting edge HTML5 specs. Chrome happens to be very good at supporting the latest specs. It's significantly more ahead than Firefox, and it's way, way, way ahead even than the latest version of IE. So if an "experiment" meant to use the latest technologies happens to "only work in Chrome", don't blame Chrome for implementing the specs much fas…
> It's an "experiment", which means it could be using some of the latest and cutting edge HTML5 specs. That's fair. > Chrome happens to be very good at supporting the latest specs. It's significantly more ahead than Firefox, and it's way, way, way ahead even than the latest version of IE. That's not accurate. Chrome is ahead in some areas, but behind in others. But the bigger point is that the site says > "We're sorr…
Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than even the latest version of IE. What you said doesn't contradict that point.
Re: Chrome World Wide Maze
#94Earlier quoted context omitted.
> It's an "experiment", which means it could be using some of the latest and cutting edge HTML5 specs. That's fair. > Chrome happens to be very good at supporting the latest specs. It's significantly more ahead than Firefox, and it's way, way, way ahead even than the latest version of IE. That's not accurate. Chrome is ahead in some areas, but behind in others. But the bigger point is that the site says > "We're sorr…
>Chrome is ahead in some areas, but behind in others. Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than even the latest version of IE. What you said doesn't contradict that point.
As for IE, I don't run Windows, so I know less about it.
Re: Chrome World Wide Maze
#95Earlier quoted context omitted.
>Chrome is ahead in some areas, but behind in others. Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than even the latest version of IE. What you said doesn't contradict that point.
I don't agree that it is "significantly more ahead than Firefox" - can you back that up? There is a long list of features that each of those browsers has, that the other does not. As for IE, I don't run Windows, so I know less about it.
Re: Chrome World Wide Maze
#96The reason this is so impressive is that it brings together three technologies that people aren't used to even seeing one good implementation of yet: * HTML5 accelerometer support * Sync between mobile/desktop using websockets * Web page slicing based (by the look of it) on DOM and image processing …and of course this is in a nice responsive WebGL-rendered package, which people are getting more used to thanks to the…
Re: Chrome World Wide Maze
#97Earlier quoted context omitted.
I don't agree that it is "significantly more ahead than Firefox" - can you back that up? There is a long list of features that each of those browsers has, that the other does not. As for IE, I don't run Windows, so I know less about it.
Chrome 463, Firefox 393 that's a fairly large gap IMO. http://html5test.com/results/desktop.html
Edit: Also, that does not include JS features at all. The modern web isn't just HTML ;)
Re: Chrome World Wide Maze
#98I think this is the first time I've been genuinely impressed with a Chrome Experiment. They've recreated Super Monkey Ball entirely inside the browser, with the option of using a device as a controller. Certainly an interesting concept for multiplayer gaming, imagine Chrome running on a Smart TV(Chrome OS TV?) and a couple of friends can hook up their mobiles as controllers, and play some casual party style games lik…
Google want to connect your browser information with your phone information. And they're doing a good job.
Re: Chrome World Wide Maze
#99This is awesome! now lets get some sweet Tux Racer or Mario Kart going! (please?)
Re: Chrome World Wide Maze
#100Earlier quoted context omitted.
>Chrome is ahead in some areas, but behind in others. Correct, but as a whole, it's significantly more ahead than Firefox, and it's way, way, way ahead than even the latest version of IE. What you said doesn't contradict that point.
I don't agree that it is "significantly more ahead than Firefox" - can you back that up? There is a long list of features that each of those browsers has, that the other does not. As for IE, I don't run Windows, so I know less about it.
* No CSS shaders
* CSS 3D is still very buggy (http://acko.net/#force3d) despite the support being over a year old now. Also renders without anti-aliasing, which makes it really ugly.
* Both Firebug and the built-in inspector seriously lack compared to Chrome's dev tools which has a per-frame timeline, profiler, etc. Instead they added the rather pointless 3D tilt view of the DOM which doesn't show you the actual DOM layers (unlike this 5 minute CSS 3D hack: http://www.youtube.com/watch?v=2-oQj9Y9I6I) and hence is just a misleading gimmick.
* No in-browser code editing/saving
* No Web Audio API
* No desktop notifications
* No MP3, no AAC, no H.264 support (on OSX anyway), the three most common audio and video codecs.
* No date/time picker, no color picker, no number range field
Yeah, I know there are reasons behind this, but still, the picture is heavily skewed in Chrome's favor
As for IE... CSS 3D support is incomplete (no nesting), its dev tools are pretty crap, and they seem to be actively ignoring standards like WebGL and pushing their own spec for WebRTC.