I'm aware of that, but don't you think the adapter code looks "nicer" without the `.new`, with adapters only touching the job _this_ much and not any more than necessary? It makes the adapters a little more robust, allowing us to change the implementation of `.perform_raw` at some point, like passing special initialization args to `job.new(...)`.
Another reason I just thought of: Adding `#perform_raw` on the instance alongside the innocuous `#perform` may cause some users to believe it's a good idea to override that on their jobs to add their own deserialization, which would mess with logging and possible future error rescuing.