Why should I "Supervise" Laravel's queue listener instead of "Schedule" it?

According to Laravel's documentation, I need:

php artisan queue:listen

To be running at all times to process queued jobs. And if I run that manually, everything is fine until it fails and then I have to rerun that command manually to get it up and running again.

If I'm using Laravel's Schedule system to run all of my scheduled commands, why would I not just that command every 5 minutes to make sure it's still running?

It seems like installing Supervisor via apt-get and creating another potential point of failure is overkill and unnecessary. What am I missing?

via Chebli Mohamed