Why is using a blocking function a problem in an asynchronous application?
When a blocking function is called, the event loop is also blocked. This means that during the whole execution of the blocking function, no other action can occur in the application. Blocking calls are often I/O-based operations that can be very long (up to several seconds sometimes). If the application is stalled for such a long period, at best the user experience is degraded, and at worst some important messages will have been lost.
Why is using a CPU-intensive task a problem in an asynchronous application?
Using a CPU-bound task leads to the same issue as using a blocking call: the event loop is blocked for a long time, and it is just a matter of time before this breaks the functioning of the application.
What is the aim of a scheduler?
A scheduler is one of the ReactiveX components that allows...
