Earlier quoted context omitted.
Local storage and Networked storage always have their places. Local solid state storage almost always gets you better performance because you negate the overhead of network. Unless, you’re talking fancy arrays connected to saturate 100G NICs. Local storage falls apart the moment you need that storage accessible from another machine…
Networked storage also falls apart the moment you need anything better than basic file storage. So many filesystem features do not work networked, most network file mounts do not support any kind of modern security and the ones that do are often super slow. Everything has its place, but I wasted so much time trying to get a nas to work as storage for my home server.
If you need reasonable access to your storage from more than one computer, you need networked storage(of any kind).
Alternatively, if you are running say a database server, and you know the primary storage could be local, it is ideal to choose better performing local storage and of course plan for backups to networked storage.
As much as I agree with your pain points of networked storage, it’s not like you can “replace” it with local storage everywhere.
I have dealt with a couple PB of networked storage for a research cluster. (FreeBSD+ZFS) over NFS on a dedicated network to a cluster of about 100 servers running recent versions of Linux. It worked like a charm while we admittedly kept things simple in terms of file system features.
All clients mount the appropriate NFS shares they need via autofs(only when they are needed).
ZFS being ZFS was just a marvel of software engineering, was solid as a rock. While giving us transparent compression, superb read caching in memory, and cheap snapshots.