▲ 597 ▼ "...is not supported in this browser", fuck you Discord (programming.dev) submitted 3 years ago by likeaduck@programming.dev to c/technology@lemmy.world 124 comments fedilink hide all child comments
[–] TheMadnessKing@lemdro.id 5 points 3 years ago (3 children) Any reason FF hasn't implemented this? permalink fedilink source parent hideshow 6 child comments replies: [–] d3Xt3r@lemmy.world 33 points 3 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 2 points 3 years ago* (last edited 1 year ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] d3Xt3r@lemmy.world 1 point 3 years ago* (1 child) AudioEncoder (bug 1749046) doesn't really have any dependencies or blockers, as far as I can tell. If there are, then you (or whoever has access) should update Bugzilla and add the dependency there. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 1 point 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent [–] redcalcium@lemmy.institute 18 points 3 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. permalink fedilink source parent [+] femboys@lemmy.blahaj.zone -30 points 3 years ago (1 child) dont show firefox users any modern web feature permalink fedilink source parent hideshow 2 child comments replies: [–] puppy@programming.dev 8 points 3 years ago (2 children) Hope you'll continue to lick the Google even after Chrome implements DRM. permalink fedilink source parent hideshow 4 child comments replies: [–] bemenaker@lemmy.world 2 points 2 years ago This isn't a chrome is bad issue, this is a discord is bad issue. They shouldn't be relying on an experimental feature. permalink fedilink source parent [–] femboys@lemmy.blahaj.zone 1 point 2 years ago im a firefox user permalink fedilink source parent
[–] d3Xt3r@lemmy.world 33 points 3 years ago* (1 child) 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. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 2 points 3 years ago* (last edited 1 year ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] d3Xt3r@lemmy.world 1 point 3 years ago* (1 child) AudioEncoder (bug 1749046) doesn't really have any dependencies or blockers, as far as I can tell. If there are, then you (or whoever has access) should update Bugzilla and add the dependency there. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 1 point 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[+] lud@lemm.ee 2 points 3 years ago* (last edited 1 year ago) (1 child) [deleted] permalink fedilink source parent hideshow 2 child comments replies: [–] d3Xt3r@lemmy.world 1 point 3 years ago* (1 child) AudioEncoder (bug 1749046) doesn't really have any dependencies or blockers, as far as I can tell. If there are, then you (or whoever has access) should update Bugzilla and add the dependency there. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 1 point 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[–] d3Xt3r@lemmy.world 1 point 3 years ago* (1 child) AudioEncoder (bug 1749046) doesn't really have any dependencies or blockers, as far as I can tell. If there are, then you (or whoever has access) should update Bugzilla and add the dependency there. permalink fedilink source parent hideshow 2 child comments replies: [+] lud@lemm.ee 1 point 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[+] lud@lemm.ee 1 point 2 years ago* (last edited 1 year ago) [deleted] permalink fedilink source parent
[–] redcalcium@lemmy.institute 18 points 3 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. permalink fedilink source parent
[+] femboys@lemmy.blahaj.zone -30 points 3 years ago (1 child) dont show firefox users any modern web feature permalink fedilink source parent hideshow 2 child comments replies: [–] puppy@programming.dev 8 points 3 years ago (2 children) Hope you'll continue to lick the Google even after Chrome implements DRM. permalink fedilink source parent hideshow 4 child comments replies: [–] bemenaker@lemmy.world 2 points 2 years ago This isn't a chrome is bad issue, this is a discord is bad issue. They shouldn't be relying on an experimental feature. permalink fedilink source parent [–] femboys@lemmy.blahaj.zone 1 point 2 years ago im a firefox user permalink fedilink source parent
[–] puppy@programming.dev 8 points 3 years ago (2 children) Hope you'll continue to lick the Google even after Chrome implements DRM. permalink fedilink source parent hideshow 4 child comments replies: [–] bemenaker@lemmy.world 2 points 2 years ago This isn't a chrome is bad issue, this is a discord is bad issue. They shouldn't be relying on an experimental feature. permalink fedilink source parent [–] femboys@lemmy.blahaj.zone 1 point 2 years ago im a firefox user permalink fedilink source parent
[–] bemenaker@lemmy.world 2 points 2 years ago This isn't a chrome is bad issue, this is a discord is bad issue. They shouldn't be relying on an experimental feature. permalink fedilink source parent