From the joblib manual:

```
This object uses the multiprocessing module to compute in parallel the application of a function to many different arguments. The main functionality it brings in addition to using the raw multiprocessing API are (see examples for details):

More readable code, in particular since it avoids constructing list of arguments.

Easier debugging:
informative tracebacks even when the error happens on the client side
using ‘n_jobs=1’ enables to turn off parallel computing for debugging without changing the codepath
early capture of pickling errors
An optional progress meter.

Interruption of multiprocesses jobs with ‘Ctrl-C’
```

Unless we use any of these features, we should simply call multiprocessing.