https://bugs.kde.org/show_bug.cgi?id=432627
--- Comment #6 from Nate Graham <n...@kde.org> --- The gist of your question is "why don't we always use kio-fuse and local paths instead of sometimes using native KIO stuff with URLs?". The answer is because native KIO operations are faster and asynchronous. They are guaranteed to never block the GUI, which FUSE mounts can do. It's not common, but it's possible. And the extra FUSE layer imposes a performance penalty. FWIW GNOME uses this same architecture: their GIO library (a rough KIO equivalent) passes URLs to GIO-using apps in an asynchronous fashion, but falls back to local FUSE paths provided by gvfs for non-GIO-using apps. -- You are receiving this mail because: You are watching all bug changes.
