Hiring managers: What do you hate about take-home assignments?

Everyone has opinions about take-home projects -- some applicants hate them, some prefer them to live coding exercises. I personally don't mind them. But with the sheer number of online testing soluti

Everyone has opinions about take-home projects -- some applicants hate them, some prefer them to live coding exercises. I personally don't mind them. But with the sheer number of online testing solutions available today, it seems like take-home assignments are still relatively low-tech: * I've seen many take-home assessments sitting in public GitHub repos. The candidate solutions are also posted to public repos, meaning that an unscrupulous candidate could simply copy another candidate's solution. * Even if you keep the repos private, an engineer will need to create new repos for each candidate. Not to mention the time spent cloning candidate solutions and evaluating them. * Nearly every application uses a database. But the attempts I've seen at replicating a database in take-homes aren't optimal, and spinning up (and tearing down) a cloud database for technical assessments is time consuming to say the least. * Not to mention all of the back and forth emails between recruiters, hiring managers and candidates. I once had a recruiter overlook my email after I had completed an assessment. Sometimes, devs are busy and delay evaluating candidate solutions, or neglect them altogether. There are alternative to take-homes, depending on the candidate, but assuming that they're relevant to the skills used on the job and aren't too time consuming, they're probably the least worst option in many cases. What problems do you encounter when administering and evaluating take-home assessments to candidates? How could the process be better or easier?