The disadvantage is that it hard to convince other people on the team, and need to use a local git pre-commit hooks, otherwise it's easy to forget to use a correct commit message, and the pain of re-writing the commit messages later ;(
IMO the most important part of the commit message is to include the issue/ticket number (if relevant).
I like the simple structure of the Linux git commits. They start with a scope, which is how the directories in the repository are organized. I would rather spend effort on coming up with proper scopes instead of categorizing commits into types. Individual commits are often part of a bigger story, so such categorization is not even that useful.
Getting folks to write decent, useful commits is hard enough. making them confirm to a parseable format wasn't worth the hassle.