Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

First, I fail to see the difference with the UX of the other smart TVs.

But mostly, as it is still Firefox OS, I don't see how people will be able to do cool multimedia applications, without access to native code and threads. Implementing DLNA, SMB, AFP shares, listening to network devices, hardware decoding, perfect audio/video synchronization requires threads and probably native code.

Limiting to HTML5 videos is going to be a very light. Or they will re-implement all the media center and multimedia code themselves, supporting all codecs and formats (and subtitles)?

I could somehow understand the limitation on the phone, but on a TV, multimedia playback is the massive use case.



Limiting to HTML5 videos is going to be a very light. Or they will re-implement all the media center and multimedia code themselves, supporting all codecs and formats (and subtitles)?

Generally on Smart TV's the video decoding isn't handled by the browser/render, instead handled by the underlying media player and hardware decoder. Pretty much all the TVs (Samsung, LG etc) use HTML5 video with much wider support for codecs then you see in browsers. HLS/H.264 is commonly supported.

Similarly they tend to use mechanisms such as custom plugins and JavaScript interfaces for DLNA/SMB etc. Not sure why you need threads in particular, there's already a lot of JavaScript mechanisms (events, async calls) to support these types of features.


All the TVs are moving to native SDKs, in order to have good games and good multimedia apps. This is true of Samsung, Sony and LG. Games on Firefox OS are a joke.

If you want extra codecs, media players or media center, you need to write them in native.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: