A file system abstraction gives editor code one interface for storage that may be local, remote, or virtual. It hides where files live, so higher-level features can work without separate implementations for each storage system. section 3.1
One editor, several storage locations
The same editor code can open a local file, a remote SSH folder, or an unsaved scratch buffer. The URI abstraction supplies a uniform address; the file system abstraction hides whether the underlying resource is on disk, a remote server, or a virtual file system. section 3.1
Figure 3.2 The ten core abstractions in VS Code, distilled from 10,000 files. The arrows show a recommended learning path, starting with foundational code like Resource Cleanup and ending with visible UI like the Workbench Layout.

Use the dependency map to place file system abstraction beneath text editing and language features, and above the URI abstraction. section 3.1
