JavaScript development tends to involve a lot of files. Between Babel, ESLint, Webpack, Post-CSS with their high number of plugins, presets, and other support m

JavaScript development tends to involve a lot of files. Between Babel, ESLint, Webpack, Post-CSS with their high number of plugins, presets, and other support modules, Typescript, testing frameworks like Jest (that comes with it's own test runner, mocking facilities, transpile-aware code coverage etc.), and general tendency for JS developers to favor composing software out of many small modules - a typical JavaScript project (browser or Node) has thousands of modules and tens of thousands of files in node_modules folder. Plus, a typical JS development process involves a filesystem-based watcher that reloads parts of an application on a fly as a developer changes code. As a result, for a very big percentage of programmers filesystem performance is crucial for their day-to-day work. There's an argument to be made that JS development ecosystem is unnecessary complex, and there are projects that try to change the status quo, but they are not ready for a prime time and aren't widespread enough yet.