This is great stuff!
One thing I didn't see in the article (sorry if I just missed it!) that might be worth pointing out is I believe (correct me if I'm wrong!) crontab will run concurrently, but SQL Server Agent will hold off on the next scheduled execution until an existing one finishes. For example, if you have a process run every minute, but it's running longer than a minute, crontab will kick off the "job" again while the previous execution is still running, but SQL Server Agent won't kick off the job if it's already running.