If you don't have specific requirements against groovy, mixing groovy/java works really well. If you use maven it's really easy to do with gmavenplus plugin or the groovy eclipse compiler. You can seamlessly have groovy and java code in the same project which allows you to use the flexibility of groovy when needed (e.g. for writing Gremlin natively) while still getting your standard Java that you are more familiar with. I'd prefer that approach over embedding groovy strings all over your project.
If all your Gremlin looks like:
_().out('knows').name
then maybe a few strings are not a big deal, but when you get to a "larger" project with really complex traversals, you probably don't want to have a gremlin string 100+ lines long in your code. I would also assume that dynamic compilation of groovy strings is less performant than compiled groovy, though i don't have numbers to support that offhand.
At the end of the day, not being familiar with Groovy is not a good reason to stick to Java. To write really concise and idiomatic Gremlin, you will need to know groovy, so you may as well start learning. :)
Stephen