zlacker

>>tobr+(OP)
I miss being able to know if my program is frozen because of CPU (fan noises), disk access (HDD noises), or network (silence).

I've thought of "reimplementing" that for troubleshooting my own projects. Imagine `clang --sounds`, so that it makes a sounds when

- Accessing disk.

- Sending something on the network.

- Allocating large buffers.

- Waiting for locks.

Or, alternatively, there's a constant background sound that is modulated on every function call depending on

- Call stack depth.

- If it's my code, library, or syscall.

- How long the last call took.

- Or just a unique modulation for each major function.

I think that's a nice, easy, and useful step before the more advanced applications mentioned in TFA.

>>Boppre+nx4
This is why I'll never try to build a silent system. Coil whine + fans communicate quite alot, but also fade into the background. Something about the noise from the fan just modulating slightly makes it less intrusive for me than a sound coming out of silence.

>>yummyp+x05
It's like living in a noisy apartment or on a busy street. Yes noise does fade into the background but subconsciously it still affects concentration/sleep/mood/creativity/etc. You won't know what you're (not) missing until you try it without the noise.