Incredibly excited for the upcoming #Nautilus#GNOME Files manager v45 release.
Assuming the handful of remaining #performance related merge requests land in time, including thumbnails multithreading, this will be the fastest, smoothest Nautilus you've ever seen on #Linux with #Tracker 3.5+
@nekohayo disappointed to see the thumbnail ticket tagged "not actionable" because "slow is vague" when the ticket was very specific about how it is slow and a number of issues were identified in the following discussion
@nekohayo@antoniof surely you can see that trumpeting "we've improved performance a ton! 🎉 Here's a list of the issues we've closed!" & then having the issue that seems to have inspired this great success closed as "stop wasting our time" ... it's not a good look
@igrok@nekohayo On the opposite side, keeping a not-actionable, negative feedback-attracting issue open after specific issues have been identified is not respectful to developers, because it's like they have done nothing to address the issue.
Like a Sisyphus punishment, where no matter how many times developers roll the performance ball up, it always rolls back down on them because it's still "slow" in some other specific way.
@antoniof@nekohayo I suggest you reread the original report. I thought it was refreshingly respectful and specific (and actionable). To paraphrase, "they thumbnail images 20x faster than us. We should look at their code and do that!" I'm really not clear what's vague and unactionable about that.
Take it as "investigate other software code strategy + file issues to resolve" (rename if needed), cite the issues filed, & call it done!
@antoniof@nekohayo instead, the issue was closed with labeling saying that it's been triaged as a low quality issue with nothing specific to act on & therefore won't be fixed. Your response at least half validates my reading.
They gave you specific numbers about a specific feature. They pointed you to specific source code. That's not a vague whine.
That attitude doesn't invite help to improve (and it was clearly helpful since it's been this way for years).
@igrok
Personally, as the one who filed that issue originally, and worked through extensively testing & troubleshooting with the devs to make it happen, I am not offended by @antoniof recently closing it in favor of the other sub-issues linked there. The general issue has pretty much served its purpose, I think.
The upcoming concurrent multi-threaded thumbnailing by itself speeds up by 3-4x (or more!) on most PCs; not 20x, but good enough for me (~1-2 secs to thumbnail the visible view here)
Add comment