Chrome World Wide Maze • Hacker News Board

Re: Chrome World Wide Maze

#121

Post by greggman » Fri, Mar 22, 2013, 5:06 AM UTC

azakai wrote: post #103

unconed wrote: post #100

Earlier quoted context omitted.

Firefox: * 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…

Those are indeed features that are missing from Firefox, yes. Although several are already there in nightly builds (WebAudio, number range, for example). As I said earlier, it is easy to compile such a list from the other direction, stuff Chrome is missing. A few off the top of my head: * A wide range of ES6 features, see http://kangax.github.com/es5-compat-table/es6/ * Proper fullscreen mode (resized) * OPUS codec *…

* asm.js is not a standard and was only announced 2 weeks ago. Hardly a fair comparison.

* ES6 features? All disabled on FF19.

* OPUS codec? Who uses that? Which codecs to support is not part of any standard. Browsers are free to support what they want. But at the same time, not being able to play the most common audio and video formats seems like a far bigger issue.

* What's "proper fullscreen mode?"

Re: Chrome World Wide Maze

#122

Post by azakai » Fri, Mar 22, 2013, 2:32 PM UTC

greggman wrote: post #121

azakai wrote: post #103

Earlier quoted context omitted.

Those are indeed features that are missing from Firefox, yes. Although several are already there in nightly builds (WebAudio, number range, for example). As I said earlier, it is easy to compile such a list from the other direction, stuff Chrome is missing. A few off the top of my head: * A wide range of ES6 features, see http://kangax.github.com/es5-compat-table/es6/ * Proper fullscreen mode (resized) * OPUS codec *…

* asm.js is not a standard and was only announced 2 weeks ago. Hardly a fair comparison. * ES6 features? All disabled on FF19. * OPUS codec? Who uses that? Which codecs to support is not part of any standard. Browsers are free to support what they want. But at the same time, not being able to play the most common audio and video formats seems like a far bigger issue. * What's "proper fullscreen mode?"

asm.js is not a standard, but neither are various things on html5test. I agree it and those other things are less important though.

Not all ES6 features are disabled? For example WeakMap.

OPUS would be used by more people if more browsers than Firefox supported it ;)

Proper fullscreen mode is fullscreen where the element has the right css, that makes it fill the screen as per the spec. Chrome does not do that yet.

Re: Chrome World Wide Maze

#123

Post by endergen » Sat, Mar 30, 2013, 11:21 AM UTC

ash wrote: post #101

endergen wrote: post #69

Earlier quoted context omitted.

Hey guys, I'm the CTO at Brass Monkey. We definitely experimented with this approach of using a webpage and websockets to communicate, it is nice that it doesn't require installing an app but it communicates via relaying messages out to the internet and back and so generally has latency in the 100ms+ ( http://www.youtube.com/watch?v=NE8-TntjYB4 With Brass Monkey we decided to instead make a single master controller a…

> a trick we discovered to communicate over LAN between your phone and PC Wow! Could you please tell a little more about the trick? How does a LAN connection between your web app in the browser and your iPhone app work? Do you create a locally accessible web server from your iPhone app?

Yes that's exactly what we do. :)

Re: Chrome World Wide Maze

#124

Post by endergen » Sat, Mar 30, 2013, 11:22 AM UTC

faceyspacey wrote: post #107

ash wrote: post #101

Earlier quoted context omitted.

> a trick we discovered to communicate over LAN between your phone and PC Wow! Could you please tell a little more about the trick? How does a LAN connection between your web app in the browser and your iPhone app work? Do you create a locally accessible web server from your iPhone app?

funny thing is I've been wondering this all day myself.

See above reply!