A lot of services *will* spambucket mail coming from a domain without SPF, but often won't outright *reject* it, because SPF was a retrofit and they wanted back-compat for postmasters that couldn't be assed to set it up. Not that they *shouldn't* codify it in the RFCs as a SHOULD eventually, just that they haven't chosen to do that yet for Internet Politics reasons.
Explicitly telling MTAs "this domain shouldn't be allowed to send email" on the other hand removes all ambiguity, regardless of future RFCs.