When defining drivers for Material Node properties,
self references the Node itself. While this may have its uses, it would be great to be able to access the object being rendered. This way you can create a single material that produces correct results for a batch of similar objects, all linking to that same material.
I'm in a situation were I had to create 40 copies of an object, all having 2 custom properties of type float. Those 2 properties are meant to control a driver defined in a material node.
The problem: that I needed to create 40 copies of the same material, reference the correct material from the correct object, and edit all drivers to change the object's name.
The process of going into all objects to edit their material slots, to copy the previous one, then unlink the previous one, then go into node editor and edit all drivers only to change the object's name is very inefficient.