I think you're both right. :) You (and the article) are right: scalaz's Task can minimize context-switching overhead. Trampolining can further reduce it. GP's

I think you're both right. :) You (and the article) are right: scalaz's Task can minimize context-switching overhead. Trampolining can further reduce it. GP's right: In most usage scenarios, this gain is irrelevant. I had the same gut reaction as the GP but refrained from commenting...until now. What bothered me most about the post is the final claim that a 3-orders-of-magnitude speedup is possible, reducing runtime of a computation to hours from weeks. That claim is only borne out if you do a very contrived example where scheduling time dominates.