This is not what’s standing in between me and shipping products that users desire. Also EOF is a solution to this problem, but not the solution to this problem. A smarter compiler (looking at you, Vyper) also solves this problem.
Like @TimDaub said, deployment costs basically don’t matter. But 9% decrease in runtime gas is pretty neat! I recant my earlier statement that there is no benefit to smart contract developers immediately on the hardfork. I think that’s still probably not enough benefit to counteract the additional pain/burden caused by the opcode changes, but I appreciate that things are moving in a beneficial direction. 
My application is more sensitive to gas consumption than most, so “gas lower” is a better reason for me to adopt EOF than it is for most projects. But I reiterate my first point: this is not what’s standing in between dApp developers and shipping products that users deesire.