this post was submitted on 15 Aug 2023
548 points (88.9% liked)

Technology

72360 readers
2763 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
548
"...is not supported in this browser", fuck you Discord (programming.dev)
submitted 2 years ago by likeaduck@programming.dev to c/technology@lemmy.world
119 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] TheMadnessKing@lemdro.id 5 points 2 years ago (3 children)

Any reason FF hasn't implemented this?

[–] d3Xt3r@lemmy.world 32 points 2 years ago* (last edited 2 years ago) (1 children)

Because Firefox is like a democracy, they prioritize work based on number of votes on issues/feature requests. The AudioEncoder API has literally just one vote, and the overall WebCodecs API that it's a part of only has five votes. This shows that there's very little demand for it, meaning very few sites actually use this (that or the vast majority of Firefox users don't use/need this feature). Why bother focusing your efforts on implementing something that most users don't care about? The higher priority things that most Firefox users care about is stuff like performance, and Mozilla have been making some good progress too on that front.

[–] redcalcium@lemmy.institute 15 points 2 years ago* (last edited 2 years ago)

This is an experimental API that hasn't been finalized yet. Firefox devs has limited engineering resource and simply can't keep up with Chrome's push to implement experimental/proposal API. Safari also hasn't implemented this yet because they also usually wait until the API finalized, which can take quite a while.