While this isn't natively supported yet, there are some tricks to achieve something like this, either with using APOC Procedures for subqueries, or, if your expansion-stop case is based on labels, APOC's path expansion procedures.
https://neo4j.com/developer/kb/limiting-match-results-per-ro...
My point is not to criticize Cypher (at all). Its learning curve is perfect. And it covers most of the requirements really well with a compact readable syntax.
Plus it improves with each version of Neo4J. Which is cool.
My point is that gremlin has been super efficient for us to express (in its functional way) tricky traversals. So I do not see any reason to discard it as a "inefficient" technology.
My point is that gremlin has been super efficient for us to express (in its functional way) tricky traversals. So I do not see any reason to discard it as a "inefficient" technology.