So this question seems to be having all it's answers merged into one gian community wiki:
As outlined Death to Community wiki, CW should used very rarely, and only with an answer is truly collaborative. This isn't the case here. It's just a question with a very broad scope which is also getting a lot of answers. Any concerns with the number of answers is a problem of the question and not the answers.
One of the major problems with community wiki, which applies here, is that it removes the ability to vote on or verify individual answers.
If answers are posted individually then the best answers rise to the top, allowing users to quickly and easily find what the community believes is the best answer to the question. With CW this just isn't possible, and instead a user needs to read through a CW consisting of unrelated answers and decide for themselves which answer is best.
Individual answers also allow the community to weed out incorrect answers, or point out a major flaws in an answer. This isn't possible with CW. If I edit in an incorrect solution to a giant CW answer the community has no way to quickly and clearly communicate this to users. I'm sure the first thing some users will think of is "Just edit it out if it's wrong", but how do we decide when a specific answer is wrong? You can't just vote on it, like you could with individual questions. Do we just edit war back and worth until people give up? Have a huge argument in the comments about it (a comment section which could very well already be flooded with discussions about other sub answers? Make a meta? all of these are terrible solutions to a problem which shouldn't even exist, because the answer shouldn't be CW in the first place (it's worth noting this same problem occurs if a user edits in a new correct sub-answer, and another user decide it's wrong).
Finally, having one giant answer is a really bad new user experience. If a new user comes along with a new solution to the problem we should be encouraging them to post more answers, not tell them to delete their answer as was done here. This is the exact opposite of the new user experience we want to create.