8 Responses

  1. I couldn’t agree more!

  2. Ah ah ah… I expected a very long article!
    Very funny!
    However I agree.
    I also think this is all about embedded sound in web pages.

  3. So we should stop audiocasting and videocasting? I don’ t think so.

  4. @TC:

    There are exceptions to every rule. Those types of “embedding” you mentioned are under the control of the user, which is fine in most cases.

  5. NashvilEric:

    What about musician websites?

    As a live music lover, I go to a musician’s website for one thing: to hear what they sound like. I want it to play right away, and I want it to work.

    It infuriates me to go to a musican’s formal, official, ‘designed’ website and have an impossible time digging to the music section, selecting a track, finding out I don’t have the right codec, etc.

    Then I find the same musician on a ghetto myspace page and can actually hear what they play. And it plays immediately. Without. any. hassle.

    I was really hoping this article had some best practices for including audio across various user agents. Hell, I even bookmarked it before I started reading.

    What I wasn’t looking for was someone sharing their opinion with no explanation or caveat.

  6. Steven:

    Impressive Webs not too impressive with this post.

  7. I would have to disagree.
    and here’s the reason: http://bit.ly/cCACCe
    (turn sound on)…

    I think for the majority of the web though, we should have the choice to hear sounds, not be forced to hear them.

  8. nykeri:

    this might become an issue when html5 is released

Comments for this post are now closed.

Read the latest articles and tutorials if you'd like to have your say.