https://bugs.kde.org/show_bug.cgi?id=75324
--- Comment #89 from Alexander Schlarb <alexander-kde@ninetailed.ninja> ---
Is there any reason by KDE really needs it's own remote vfs abstraction system
and cannot use GIO/GVFS instead as suggested in comment #6? (There is even some
code to start off for inspiration from even if its like 10 years old.)
Some selling points GVFS/GIO has over KIO (mostly subjective, but meh):
* Already has the mentioned FUSE layer
* Used and maintained outside the KDE community
* Copying many small files (locally!) is a lot faster
- (Although it's still insanely slower than good old `cp A B`.)
* Finally having a standard would probably make a lot more external devs
happy to add native support for this (I don't think that standard could be KIO,
since it's so KDE/Qt/C++-centric while GIO basically only requires GLib)
* (Doesn't crash on MTP [might just happen to be an issue with all mobile
devices I ever owned, but it never happens when using GIO instead].)
I'm honestly interested in the devs opinions here since: There may well be
something obvious I'm not seeing.
--
You are receiving this mail because:
You are watching all bug changes.
