Things may have changed since then, but when I first encountered the project several years ago it seemed like the thing that made this project stand out compared to other player projects was a big emphasis on correctness and accurate playback. There have files I’ve encountered that for example VLC will play with quirks (color reproduction is not quite right, etc) that mpv plays perfectly.
Given how VLC is basically bulletproof and will play absolutely anything thrown at it - it's great to hear that mpv is up there ...
Sad to hear.-
PS. On a tangent, rethorically - baring bugs and security - at one point is (if ever) software "finished"?
"We built this search engine. It works. The infrastructure has team enough to run it. But we have this huge payroll of people."
So "improvements" and "features" (and constant UI and UX changes) ...
... "enshittification" ensues.-
When is "good enough" ... good enough?
A media player, though, has fewer challenges.
“PS” originates from “post scriptum”, meaning “written after”. It doesn’t make sense to have it at the start of the text.
But to answer your question, yes, it is definitely possible for software to be done and finished. I’ve done it multiple times, where I have built something that does exactly what I set it out to do, it does it fast and without bugs and has been doing so for years and years with zero maintenance needs.
The general obsession with the idea that “software is never done, only abandoned” needs to end, it’s harmful to good software and its users.
Here’s millions more examples of finished software, in a single word: games.
My thinking was along those lines. Or at least along the lines of "engineering and/or organizational processes should exist to know when to stop".-
PS. Thanks for your attention to detail. It was a "PS" to an otherwise one-sentence comment.-