moarsel

I see several comments along the lines of "who is this even for", which may be classic HN negativity or maybe the docs don't make it clear enough. I've actually played with this library (and many others), and I'm super psyched to see it ship!

To me this is the equivalent of React native for audio: describe your audio declaratively, and let the platform handle the rest. The benefits are:

- Write once, deploy everywhere (building DAW plugins sucks, and most web audio is not performant)

- Lower barrier to learning DSP (yes, DSP engineers already know low level languages that can do this, AND now more people can build audio software)

- Modern dev environment and faster feedback loop. I can now build a React app (or React native) with a high performance audio engine built right in.

I'm pretty skeptical of people defending the status quo approach here... Like, where's the Figma for DAWs? Why don't more more people to write their own VST plugins? And why is audio software so UGLY?

Audio software design has been stuck in the 90's for too long and I'm psyched to see it open up and become more accessible!

Nothing but praise for Greg's work, I've worked with him in person and his evidence based approach works wonders.

Apply the lessons in the book anytime you need to teach people then you'll realize how much time you wasted before. Many of the lessons are not limited to technical subjects either.

Building a concept map, for example, forces you to distill what you're trying to teach instead of trying to cram as much knowledge as you can into a lesson.

Somewhat related is "Enlightenment 2.0" - Joseph Heath Politics professor explains why contemporary politics is becoming irrational by showing how certain cognitive biases in the political atmosphere make political deliberation more difficult.

If you are interested in economics, cognitive biases, and why governance is so bad, it is a must read.