When it comes to debounce and throttle developers often confuse the two. Choosing the right one is, however, crucial, as they bear a different effect.
ArticleIn this article, the author explain the difference between debouncing and throttling. Debouncing is akin to waiting until you stop receiving events and then responding to a single event while throttling is responding to an event every X seconds regardless of how many events occur. The difference is subtle (especially when using either one leads to the same system behaviour) but understanding the diffeence comes in handy depending on what you're working on.
Along with authentication and authorization, these are another pair of terms that people (including me) have used interchangeably when they probably shouldn't have. Like most things, once you actually have to build a project where understanding the difference is vital, it becomes so obvious that you ask yourself how you ever mixed them up in the first place.
Thanks for reading and as always, all comments, critiques and questions are highly appreciated. Here's a link to the
previous article response.