macOS Finder is still bad at network file copies

Original Article ↗ Hacker News Discussion ↗

macOS Finder’s handling of network file operations, especially over SMB, is widely described as slow, flaky and buggy compared with Windows and Linux, prompting many users to fall back on command‑line tools, third‑party file managers, or NAS web interfaces for large transfers and backups. Commenters highlight long‑standing quirks such as unreliable reconnects, poor performance with many small files, Finder UI frustrations, and filesystem debris like `.DS_Store` and resource‑fork sidecar files littering non‑Apple volumes. Some tie these problems to Apple’s strategic focus on iCloud and tightly controlled hardware storage, arguing that on‑prem network storage and power‑user workflows have become second‑class citizens on modern macOS.

macOS network file copies & SMB/NFS issues

  • Many report unreliable SMB behavior on macOS: random disconnects, re‑auth failures that require reboot, slow thumbnail rendering, and multi‑second delays opening simple files from NAS.
  • Some say SMB, NFS, and iSCSI are all buggy or slow on macOS; iSCSI needs third‑party tools and performs poorly.
  • Workarounds discussed:
    • Connect via IP address (smb://ip) instead of hostname; name-based access is described as especially flaky.
    • Use mDNS/Avahi tricks to advertise SMB like old AFP shares, which some say improves caching/lookup.
    • Prefer NFS for performance with NAS boxes (e.g., Synology) when SMB tuning fails.
    • Use NAS web UI, SFTP/ssh, or third-party tools when Finder over SMB is too unreliable.
  • A few report mostly smooth SMB experience with careful tuning (Apple’s own SMB guidelines, jumbo frames, disabling Wi‑Fi, ensuring SMB3, disabling .DS_Store on network volumes).

Finder usability & UX complaints

  • Many describe Finder as fundamentally awkward: weak icon view behavior, no obvious “up” button, hidden disks, confusing column view in save dialogs, and odd selection behavior.
  • Frequent annoyance: Enter/Return renames instead of opening; defenders cite historical convention and reduced accidental mass‑open, critics argue it’s unintuitive.
  • Hidden but useful features: Cmd+Up/Cmd+Down for parent/child navigation, title‑bar path menu, “Show Path Bar,” typing to jump to filenames, Quick Look (Space), “Inspector” for multi‑file info.
  • .DS_Store and resource fork artifacts (._*, __MACOSX) on non‑Mac volumes are widely disliked; some disable writing them on network shares.

Comparisons to Windows & Linux

  • Several see Windows Explorer as “good enough” and more reliable for local/network copies; others note Win11 regressions (slower, confusing context menu).
  • Some argue Finder’s feature set (Quick Look, spring‑loaded folders, etc.) is richer but undermined by bugs and poor performance.
  • Linux file managers (Dolphin, Nautilus/Thunar) are described as mixed: better in some ways than Finder, but with their own remote‑FS quirks.

Storage models, iCloud, and strategy

  • Multiple commenters suspect Apple’s expensive internal storage and iCloud subscription focus reduce incentives to make LAN/VPN file workflows (NAS, Time Capsule‑like devices) first‑class.
  • Creatives often end up with “stacks of external drives”; some see that as a robust, redundant, portable workflow, others question backup and retrieval pain.

Alternatives and coping strategies

  • Common tools to bypass Finder: command line (rsync, ditto, scp), Carbon Copy Cloner, third‑party file managers (Forklift, Path Finder), and remote tools (Transmit, Mountain Duck, File Browser Pro).
  • Some largely avoid Finder for serious file operations, citing long‑standing bugs and a sense that Apple is deprioritizing the Mac as a “tool” in favor of cloud‑centric, console‑like usage.