3 ms·
I still remember being shocked at the bloat. It sat there eating something like 100x the memory of my entire sound stack before that (granted, easy to hit a lar
by yamtaddle 4y ago
I still remember being shocked at the bloat. It sat there eating something like 100x the memory of my entire sound stack before that (granted, easy to hit a large multiple when the baseline is very low), with pretty frequent CPU spikes, all while no sound was playing. WT actual F. And the CPU use was straight-up vulgar when it was actually doing anything.
It was then that I decided whoever was responsible for it had no software-architectural taste whatsoever. I didn't yet know his name. His work since then hasn't changed my mind.