[ilyt]

It does if you implement it wrongly.

I've seen implementations where the CPU gets the pulse, waits for debounce interval, check whether the pulse is still happening and only then sends "the button is on" signal, which obviously is terrible for latency.

Proper debounce will send signal immediately then ignore the state for few milliseconds.

> Debouncing is about preventing inappropriate deactivation, and is unrelated to time to initial activation.

It's both. Contacts generate noise on both press and depress.