I don’t know who the Web Audio API is designed for
2 comments · api, javascript
- Comments2
–Rank now
#3Peak rank
1Days on list
50Score · 7d
Oct 31, 2026First seen
On Lobsters
apijavascript
- Score
- 13
- Comments
- 2
- Submitted by
- friendlysock
- Tags
- api, javascript
- Site
- blog.mecheye.net
Story details from Lobsters ↗ · linked article on blog.mecheye.net.
Trending history
I don’t know who the Web Audio API is designed for was first seen on Lobsters · Hottest on Oct 31, 2026. Since then it has appeared in 1 check on 1 different day. Its best position was #3 of 25, reached on Oct 31, 05:21 UTC. It dropped off the list after Oct 31, 05:21 UTC.
Rank history
Position on Lobsters · Hottest at every check (lower is better).
Last 14 days
Best rank per day (UTC).
3
Oct 18today
From the discussion
A few top-level comments from Lobsters, shortened. Read the full thread on Lobsters.
Whenever I'm looking for a wel designed audio API, I always look towards this high quality C++ library : https://www.music.mcgill.ca/~gary/rtaudio/ Hopefully, some spec can be done for "pull" style audio API for the web. The rest can clearly be done with the existing APIs.
That API seemingly forces you to use threads. I don't like it. From glancing the docs, I don't see how to calculate latency either. streamTime looks like a clue but the docs are vague about it: https://www.music.mcgill.ca/%7Egary/rtaudio/RtAudio_8h.html#a112c7b7e25a974977f6fc094cef1a31f
Questions
Is I don’t know who the Web Audio API is designed for trending on Lobsters right now?
Not at the moment. It was last on the list on Oct 31, 05:21 UTC, after 1 day of trending.
What is the highest rank I don’t know who the Web Audio API is designed for reached?
#3 on Lobsters · Hottest, on Oct 31, 05:21 UTC. Trendoday checks this list every 30 minutes.
How long has I don’t know who the Web Audio API is designed for been trending?
It was first seen on Oct 31, 2026 and has been on the list on 1 day (1 check) since.