"While it is not intended to be Chrome-only, no attempt has been made to avoid using facilities which are not yet implemented in other browsers. Safari (Mac, 7.0.4) is known to work functionally but with broken flexbox UI layout, and Firefox (29) doesn't work at all (WebSocket fails to connect). Currently, the client must have the same endianness and floating-point format as the server"
For someone's personal project I'm not sure why anyone would choose to avoid the new shiny features of their preferred browser given that those features will wind up in the others eventually. It was the same situation with HTML5 where devs jumped at the ability to write code that was forward compatible and to hell with any 'legacy' browser that wasn't modern enough.
For community OSS projects I would never expect them to spend time mucking about with cross browser compatibility given that they will be eventually consistent.
As the author, I'll say that there's a large amount of "ooh shiny bleeding edge" and "if it works for me it's fine" going on. I see that newer Safari has a _different_ failure mode and I should look into that… okay fixed https://github.com/kpreid/shinysdr/commit/67327273
Isn't modern web technology great?