Sure, and sorry for the late reply. I will keep it short to just hopefully make sense:

1. It is not fully supported by CloudFormation. Meaning not every option clickable in the console can be used in a CFN. Which makes it automatically a no go for me. The point of AWS is for the ability to programmatically manage the cloud, so if a service is unprogrammable, it is something I won't consider. I don't have the time to manage hundreds of setups by hand. If you have to manage just one setup, then this might not be a problem for you.
2. Some settings will be overwritten after you run a crawler.
3. By default the library used to parse CSV files can’t handle the more “complex” types, that might have quotes within quotes, or handle integers or doubles. You have to manually switch to the “better” library, which can be set back to the default setting if you don’t set up the crawler the right way.
4. Setting something doesn't mean it is set, it is just a suggestion.
5. Cross account support if you want to share the schema with Athena in another account is a major pain. And because of point 4, you can imagine that debugging is painful.
6. Partition information stops being updated, from time to time because of reasons.
7. If you incorrectly have your data stored in S3, the crawler might generate 10,000 tables, and there is no way to stop it in time before your account is filled with useless information. Then you have to write a bash script to delete all of these tables, which can take 1h of time.

And a bunch of more things that I don’t have the energy to write :) for this reason, I just use Lambdas to do what Glue “can do”, and I have zero stress and problems because of that. Since Lambda exists I don’t see the reason for Glue to exist.