anchor.diff:  a script can simply reference them directly as:
   
   [source,java]
  +----
   client.submit("g1.V()")
   client.submit("g2.V()")
  +----
   
   While this is an acceptable way to submit scripts, it has the downside of forcing the client to encode the server-side
   variable name directly into the script being sent.  If the server configuration ever changed such that "g1" became
  
positive.code: language's JSR-223 `ScriptEngine` implementation.
  
  [source,java]
  g.V().out("knows").map(Lambda.function("it.get().value('name') + ' is the friend name'"))
  g.V().out("knows").sideEffect(Lambda.consumer("println it"))
  g.V().as("a").out("knows").as("b").select("b").by(Lambda.<Vertex,Integer>function("it.value('name').length()"))
  
  Finally, Gremlin `Bytecode` that includes lambdas requires that the traversal be processed by the
  `ScriptEngine`. To avoid continued recompilation costs, it supports the encoding of bindings, which allow Gremlin
  
negative.code: g.V().valueMap(true)
  g.close()
  ----
  
  [source,java]
  ----
  GraphTraversalSource g = traversal().withRemote("conf/remote-graph.properties");
  