Okay, I’m generally on the side if dolphin UI-wise, but when it comes to the topic of lagginess, it has to be said that dolphin, and in fact, almost everything using the kio infrastructure, is the one shitting the bed here. You’d think a bit of multithreading will keep the UI from freezing up whenever the underlying I/O has some minor hiccup (which can absolutely happen in practice with network filesystems or USB sticks in combination with large file transfers), but apparently dolphin can’t do that.
Admittedly I use an NVMe drive but I’ve never had this happen once in the years I’ve been using KDE. Dolphin is so much snappier than Windows Explorer on the same hardware that it’s almost funny.
But… Why? It’s just a mediocre and laggy copy of Dolphin.
Okay, I’m generally on the side if dolphin UI-wise, but when it comes to the topic of lagginess, it has to be said that dolphin, and in fact, almost everything using the kio infrastructure, is the one shitting the bed here. You’d think a bit of multithreading will keep the UI from freezing up whenever the underlying I/O has some minor hiccup (which can absolutely happen in practice with network filesystems or USB sticks in combination with large file transfers), but apparently dolphin can’t do that.
Admittedly I use an NVMe drive but I’ve never had this happen once in the years I’ve been using KDE. Dolphin is so much snappier than Windows Explorer on the same hardware that it’s almost funny.
Yeah, slow network mounts, especially rclone mounts, are typical examples of this.