Search
1000 results for “data0”
-
Excellent article explaining audio frequency analysis in #JavaScript
-
Excellent article explaining audio frequency analysis in #JavaScript
-
Excellent article explaining audio frequency analysis in #JavaScript
-
Excellent article explaining audio frequency analysis in #JavaScript
-
Excellent article explaining audio frequency analysis in #JavaScript
-
@inpc secret preorder is up!!! But I'm letting it out, right here and right now:
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
#TIL from building a web audio player (for the mixes):
#Safari's #opus support is still quirky. With a #webm container, playback works but AnalyserNodes won't receive anything to compute frequency data with. With #ogg, `getByteFrequencyData()` works, but the audio element calculates the wrong duration, prob. b/c it always assumes CBR. Also if you build the audio pipeline before the first user interaction in Safari, nothing will get routed to the speakers
But still, the #WebAudioAPI is awesome!
-
Stanisław Lem died 20y ago today, a brilliant #scifi #author and #philosopher, best known for his 1961's novel Solaris.
He envisioned many technologies before they really happened, including the internet and how it would lead to the fractured, post-truth political world we live in today (1968's His Master's Voice).
Having used the actual internet decades later, he also said: "Until I started using the Internet, I hadn't known there were so many idiots in the world."
https://culture.pl/en/article/13-things-lem-predicted-about-the-future-we-live-in
-
Stanisław Lem died 20y ago today, a brilliant #scifi #author and #philosopher, best known for his 1961's novel Solaris.
He envisioned many technologies before they really happened, including the internet and how it would lead to the fractured, post-truth political world we live in today (1968's His Master's Voice).
Having used the actual internet decades later, he also said: "Until I started using the Internet, I hadn't known there were so many idiots in the world."
https://culture.pl/en/article/13-things-lem-predicted-about-the-future-we-live-in
-
Stanisław Lem died 20y ago today, a brilliant #scifi #author and #philosopher, best known for his 1961's novel Solaris.
He envisioned many technologies before they really happened, including the internet and how it would lead to the fractured, post-truth political world we live in today (1968's His Master's Voice).
Having used the actual internet decades later, he also said: "Until I started using the Internet, I hadn't known there were so many idiots in the world."
https://culture.pl/en/article/13-things-lem-predicted-about-the-future-we-live-in
-
Stanisław Lem died 20y ago today, a brilliant #scifi #author and #philosopher, best known for his 1961's novel Solaris.
He envisioned many technologies before they really happened, including the internet and how it would lead to the fractured, post-truth political world we live in today (1968's His Master's Voice).
Having used the actual internet decades later, he also said: "Until I started using the Internet, I hadn't known there were so many idiots in the world."
https://culture.pl/en/article/13-things-lem-predicted-about-the-future-we-live-in
-
Stanisław Lem died 20y ago today, a brilliant #scifi #author and #philosopher, best known for his 1961's novel Solaris.
He envisioned many technologies before they really happened, including the internet and how it would lead to the fractured, post-truth political world we live in today (1968's His Master's Voice).
Having used the actual internet decades later, he also said: "Until I started using the Internet, I hadn't known there were so many idiots in the world."
https://culture.pl/en/article/13-things-lem-predicted-about-the-future-we-live-in
-
#NavigationAPI is now baseline and it's so nice!
- No more click listeners on `<a>` tags, fighting with history state, manually updating the #dom, listening for popstate events
- handles scroll position
- ties in with the #ViewTransitionsAPI -
RE: https://mastodon.social/@bagder/116153056914895130
#TheSerialPort YouTube channel is on a roll!
Last month they published a high-quality documentary about the origins of internet telephony (the og "IPhone"), featuring original interviews with the people directly involved.
Just 3 weeks later, they're following up with #curl, featuring @bagder .
-
RE: https://mastodon.social/@bagder/116153056914895130
#TheSerialPort YouTube channel is on a roll!
Last month they published a high-quality documentary about the origins of internet telephony (the og "IPhone"), featuring original interviews with the people directly involved.
Just 3 weeks later, they're following up with #curl, featuring @bagder .
-
"This reflects a #businessculture obsessed with outcomes while treating outputs as speed bumps. But outputs (#code, #design, #products) are the load-bearing work—the actual prerequisites for the outcomes desired. Focusing on outcomes while ignoring outputs means hiding in abstractions […] These tactics may get you profit, but you sacrifice benefit. The climb may feel like progress, but at the end you’ll find yourself at the top of a mountain of #lemons."
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
All hardware is supported, there are no known bugs and you even get OTA updates once a month including the latest security patches from #Google. At 7 years old, it's still a perfectly usable daily driver.
But what about the #Teclast tablet? It got stuck on #Android5.1 right out of the gate, only receiving a few patch updates. And you can see why: It sports a rather esoteric #Intel #i686 (32-bit x86) SoC and being a very cheap device, it was not economically feasible to keep it updated.
[2/4]
-
This is such a good article, anyone (any real person anyway) doing open source should read it! 👏👏👏 @andrewnez
> #GitHub made #forking a one-click operation a decade ago without ever investing in making the resulting graph navigable […] A pull-based model would sidestep most of this, because #agents can #fork and generate garbage all day without anything landing in anyone’s inbox.
-
Probably a good time to repeat myself:
- Run your #node-based prod app **AND** dev stack in isolated #containers / #vms (most malware targets you, the dev!)
- Use as few external packages as possible
- Check all packages carefully before installing, incl. updates (grab tarball and use #diff when in doubt!)
- What you see in a module's #GitHub is not necessarily what's on #npmAnd btw, the issue lies with npm and the move-fast-and-break-things culture, not #javascript
-
I enjoyed this article on #vim #minimalism, even though it's a bit too extreme for my taste. I too try to keep my setup as lean and use as much built-in functionality as possible. But I still think syntax highlighting and LSPs are genuinely useful. #LSP feedback should be entirely on-demand of course. And compiling commits with #fugitive is just so much faster and more flexible than with the #git #cli. But apart from that… right on!
-
@seanhood You could try solving the #AdventOfCode with #VimScript ;-) Nah, better not. AoC should be about having fun.