Update readme

Author: Christopher Schnick

FS.md

@@ -0,0 +1,11 @@
+## Why the Java FileSystem API is bad
+
+### No distinction between absolute and relative paths
+
+    void checkFile(Path target, Path toCheck) {
+        FileSystem fs = FileSystems.newFileSystem(target, Map.of());
+        fs.
+    }
+
+One easy solution to this would be to create a `AbstractPath` class
+that only supports operations applicable to all types of paths and is not bound to a file system.

README.md

@@ -4,22 +4,26 @@ This library provides a simple file system to access the contents modules in a u
 
 ## Motivation
 
-Since version 1.7, Java provides the
-[FileSystem](https://docs.oracle.com/javase/7/docs/api/java/nio/file/FileSystem.html) and
-[Path](https://docs.oracle.com/javase/7/docs/api/java/nio/file/Path.html) classes, which make working with files much easier.
-
-However, to reliably access resources in a package of a jar, or now a module, you still have to use the old methods
-[getResource()](https://docs.oracle.com/en/java/javase/15/docs/api/java.base/java/lang/Class.html#getResource(java.lang.String)) and
-[getResourceAsStream()](https://docs.oracle.com/en/java/javase/15/docs/api/java.base/java/lang/Class.html#getResourceAsStream(java.lang.String)),
-because modules can be stored in different formats:
+The [Path](https://docs.oracle.com/javase/7/docs/api/java/nio/file/Path.html) and
+[FileSystem](https://docs.oracle.com/javase/7/docs/api/java/nio/file/FileSystem.html) APIs
+introduced in Java 1.7 with NIO.2 makes working with files much more pleasant.
+One hurdle when trying to use these APIs with bundled application resources is that modules can be stored in different formats:
 - Exploded module directory, stored as directory tree (Used during development)
 - Module artifacts, mostly stored as jars (Used for both development and production)
-- Modules contained in a JLink image in a proprietary jimage format (Only used for production)
+- Modules contained in a jlink image, which are stored in a proprietary jimage format (Only used for production)
 
-While there are FileSystem implementations like jdk.zipfs for jar files and the internal jrtfs for jimage modules,
-there is no unified interface and you have to take care of FileSystem specific differences like ... and closeabilty.
+While there are FileSystem implementations like jdk.zipfs for jar files and the internal jrtfs for jlink images,
+there is no unified interface, which results in you having to take care of FileSystem specific differences like ... and closeabilty.
 As a result, how to access files in modules using FileSystems depends on how the modules are stored
 and can therefore vary between development and production environments.
+The current solution to reliably access resources in a package of a jar, or now a module, is to use the old methods
+[getResource()](https://docs.oracle.com/en/java/javase/15/docs/api/java.base/java/lang/Class.html#getResource(java.lang.String)) and
+[getResourceAsStream()](https://docs.oracle.com/en/java/javase/15/docs/api/java.base/java/lang/Class.html#getResourceAsStream(java.lang.String)).
+These methods are however way more tedious to work with.
+
+
+
+
 
 ## Features