When a question is edited it shows back up on the recently active questions. People read it again and it takes time from people. Deleting a question removes it from view and allows the OP (if he or she should desire) to be able to edit it (you can edit deleted posts if you can see them - such as 10k users and the OP can) and flag it for undeletion. In the meantime, deletion prevents further down votes of the question and can reduce the comment drama that can detract from the rest of the site.
Most recently, this happened with the question Steps for App Development? (10k link):
The original version:
App Development minimal knowledge
I want to create some mobile and web applications quickly. I am aware of the 'full stack' but I do not know any of its associated technologies. If I were to use 'back-end as a service' what is left for me to do in deploying an app besides simply coding it?
The edited version:
Steps for App Development?
I want to create some mobile and web applications quickly. I am working in 'full stack' environment but I do not know any of its associated technologies. If I were to start there and use 'back-end as a service' what additional steps do I need to take in deploying an app besides simply coding it?
And the comments on it:
meta.programmers.stackexchange.com/questions/6483/… – gnat yesterday
I made the question "less broad" by asking for "additional steps," and wonder if it can be re-opened in its current form. – Tom Au 22 hours ago
@TomAu that still doesn't make it not too broad. What technologies are known? What end result is desired? Mobile and web apps are very different. Is this android or iOS or that windows phone thing? Do you even have the right hardware? If we're talking about web apps is this to be on the intranet? or the cloud? There is much more information that the OP needs to provide to make this an answerable question. – MichaelT 22 hours ago
With this question, I can think of dozens of ways to answer it for various combinations of technology. For ruby, it would be one thing, for a php another, for python another, for the .NET suite another, for Java yet another. And then I'd answer it answer it differently if this was being deployed on the corporate intranet vs putting it out in the intranet... and then there's the mobile bit that is very different from web apps.
In this case, the OP doesn't even know where to begin and no amount of tweaking of the question will change it from that unless the OP provides the additional information about the actual problem being encountered and the path they are trying to follow.
The comment that gnat provided to Why was my question closed or down voted? exactly details what is wrong with the question and that all of those things need to be fixed before it is reopened.
Deleting the question prevents people from spending additional, undue time on the question. Questions that don't fix the close reason (and really fix it, not just a slight narrowing of scope) don't get reopened. Transforming it from one close reason to another (for example, unclear to a poll) is also not a useful edit. Consider how the question would be answered and if those answers would be ones that meet the desired quality of Programmers.SE's answers. If there are too many possible answers or the answers would require pages of tutorials then it is still too broad.
Bumping a heavily down voted closed (or on hold) question will draw increased scrutiny of the question which, if it's not a good question, can lead to it getting deleted more rapidly than the roomba would (and in some cases because the roomba won't).
If there is an edit to be made, fix all of the problems and make it into a good question not just a less bad one. Alternatively, ask clarifying comments for the OP to respond to (and if the OP puts it in the comments, then edit those comments into the question).