On Fri, Oct 28, 2011 at 5:29 PM, Gen Kanai <
gka...@gmail.com> wrote:
> Safari/iOS supports ALAC today.
>
> Webkit/Chrome, if it doesn't today, may soon provide support for ALAC,
> now that is is OSS.
>
> Considering the popularity of the iOS platform and Webkit, and our need
> to be competitive, we should seriously consider support of ALAC. The
> gaming use case is certainly one, but it seems to me a much more limited
> use case than music on the web, which is a very popular use case.
>
Given high-quality lossy formats compress much better and sound just as good
to almost everyone, why would someone use a lossless codec for music on the
Web?
I don't really understand the game situation. Assuming your game data comes
over the network I expect you'd want to use a lossy codec there too.
Apparently ALAC requires the MP4 container format which is likely to be a
problem.
The Web is best served by minimizing the number of codecs a browser needs to
support, subject to a) compatibility with existing Web content and b)
quality solutions to various author use-cases. So we shouldn't introduce a
new codec unless it's needed for compatibility with existing Web content, or
it meets some author need that currently supported codecs don't meet, or it
performs much better than the currently supported solution for that need.
The case for ALAC should be made in those terms.
Rob
--
"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]