You can manipulate the Stream as you would with any other Stream for example you might want to filter() or map() or limit() or skip() etc.
I started using this all over my code until I was hit with this exception,
Caused by: java.nio.file.FileSystemException: /tmp/date.txt: Too many open files in system
For some reason I had too many open files! Odd, doesn't Files.lines() close the file?
See code below (run3()) where I've created reproduced the issue:
My code looked something like run3() which produced the exception. I proved this by running the unix command lsof (lists open files) and noticing many many instances of date.txt open. To check that the problem was indeed with Files.lines() I made sure that the code ran with run1() using a BufferedReader, which it did. By reading through the source code for Files I realised that the Stream need to be created in an auto closable. When I implemented that in run2() the code ran fine again.
In my opinion I don't think that this is not particularly intuitive. It really spoils the one liner when you have to use the auto closable. I guess that the code does need a signal as to when to close the file but somehow it would be nice if that was hidden from us. At the very least it should be highlighted in the JavaDoc which it is not :-)