I agree that the old name is pretty bad because it's implementation-specific. I think `run`, however, will be too easily confused with a method to start a worker process. The `fork_and_perform_job()` currently executes a single job, after setting up a safe context for it (e.g. a forked child process).

I would also really like to extract out a method for [the inner worker's loop body](https://github.com/selwin/rq/blob/rename-worker-method/rq/worker.py#L295-L326). Naming things here is delicate.

Proposal:
- Extract out a method for the inner work loop's block and name it `fetch_and_execute_next_job()`;
- Rename the `fork_and_perform_job()` method to `execute_job()`. If subclassed workers need to setup a safe execution context (like the forking worker), they may do so as part of the `execute_job()` function.

Anything I'm missing?