That ("open") seems reasonable for a bug in the current release or a previous release that is still in wide use. Is there ever a situation where a bug exists s

That ("open") seems reasonable for a bug in the current release or a previous release that is still in wide use. Is there ever a situation where a bug exists so far back in the history of the project that it doesn't make sense to fix? I'm asking this as an honest question and not a challenge. I can expect that some users still use what I'd consider to be legacy S/W but I wonder how far that goes back. If the developer(s) designate a version as EOL does it make sense to keep the bug open? And OTOH, it conveys information if the developer marks a bug as "won't fix" rather than leaving the expectation that it might be addressed, someday.