Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The sound of GitHub

choir.io

Post reply on HN
Print view View original

21–27 of 27 posts

Re: The sound of GitHub

#21

Post by alexdong »

snogglethorpe wrote: post #16

Neat concept, but browser sound support seems ... dodgy... Ipad: no sound; Firefox 24 on android: instant browser crash; Chrome on android: finally works.

Audio support on mobile devices is ... shitty. You're right that there is no sound on iPad but weirdly enough, iPhone+Safari seems to work, at least last time I checked.

Our focus in the next 2-3 months is on the desktop clients. We'll release a OSX desktop app next week, then a Windows app after that. Mobile is crucial in the long run but unfortunately we can't do much until the browser vendors provide better support for playing sounds.

Re: The sound of GitHub

#22

Post by alexdong »

trycatch wrote: post #19
alexdong wrote: post #13

Earlier quoted context omitted.

Hey, that's not quite true. ;-) I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? Have you tried refreshing it? Which version/OS? We use howler.js to play the sounds. I have to say that I was a bit surprised to find Chrome/Safari/IE can play mp3 but Firefox plays ogg. I even had to submit a patch[1] so that howler.js can work on firefox under…

I tried Linux x64/FF23 and FF Nightly on a clean profile, and both leaked insane amounts of memory on this page, hundreds of KiBs per second. Interesting that according to about:memory, memory used by tab with choir.io stayed stable, but "heap-unclassified" grew uncontrollable. Bug in Firefox?

This is fascinating. Thanks for sharing.

My gut feeling is that those leaks are the "socket connections" that Firefox hasn't garbage collected yet. The demo you are seeing is using long poll so there might be some good number of socket churns.

FWIW, WebSocket support is high on our priority list. We just need to find the time to implement that.

Re: The sound of GitHub

#23

Post by CrLf »

alexdong wrote: post #13
CrLf wrote: post #12

What's up with this trend of doing stuff that only works on Chrome? On Firefox this works for a minute and then stops working.

Hey, that's not quite true. ;-) I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? Have you tried refreshing it? Which version/OS? We use howler.js to play the sounds. I have to say that I was a bit surprised to find Chrome/Safari/IE can play mp3 but Firefox plays ogg. I even had to submit a patch[1] so that howler.js can work on firefox under…

Firefox 23.0.1 on Windows here. No extensions other than Firebug 1.12.1.

Re: The sound of GitHub

#24

Post by alexdong »

benjojo12 wrote: post #17

Is there any possibility that we can also hear the small projects?

We chose neutral, low intrusiveness sound for the small projects. If you listen carefully, you should be able to distinguish the quick and light taps. It's much faster than the other sounds. The text stream will move too fast to be readable if we also display the contents from the small projects.

Re: The sound of GitHub

#25

Post by alexdong »

CrLf wrote: post #23
alexdong wrote: post #13

Earlier quoted context omitted.

Hey, that's not quite true. ;-) I wrote most of our javascript on firefox. My firefox has no add-ons except the Firebug. Could it be one of your extensions? Have you tried refreshing it? Which version/OS? We use howler.js to play the sounds. I have to say that I was a bit surprised to find Chrome/Safari/IE can play mp3 but Firefox plays ogg. I even had to submit a patch[1] so that howler.js can work on firefox under…

Firefox 23.0.1 on Windows here. No extensions other than Firebug 1.12.1.

Roger.

Re: The sound of GitHub

#27

Post by cocoflunchy »

alexdong wrote: post #21
snogglethorpe wrote: post #16

Neat concept, but browser sound support seems ... dodgy... Ipad: no sound; Firefox 24 on android: instant browser crash; Chrome on android: finally works.

Audio support on mobile devices is ... shitty. You're right that there is no sound on iPad but weirdly enough, iPhone+Safari seems to work, at least last time I checked. Our focus in the next 2-3 months is on the desktop clients. We'll release a OSX desktop app next week, then a Windows app after that. Mobile is crucial in the long run but unfortunately we can't do much until the browser vendors provide better suppor…

Why not a mobile app before a desktop app then? It would allow you be everywhere.
Post reply on HN