This is true for just about all research.
Newton "solved" the equations of gravity, Einstein "solved" them too, and now quantum mechanics is "solving" them yet again. None are wrong, but also none of them make the problem solved.
The idea of a "solved problem" in science is a dangerous one IMHO.
There are two sorts of problems in science: coming up with assumptions and answering questions under these assumptions. I was thinking about the second category. Modeling gravity falls in the first category, where problems are a lot like engineering problems - there is no final answer.
However, problems in the second category often have final answers (let's not bring Gödel's incompleteness theorem to the table) once you bring all the assumptions with you. Think about: in classical mechanics, what are the possible planet trajectories? This problem has already been solved, and since it is solved, it is solved for good. Later students can simply learn the solution by heart. You can, of course, insist to go through all the trouble of finding out the answer - that is what physical majors often do anyway - but the point is that you don't have to as long as you trust the science community.
In software development you don't have this luxury. First, you can almost never trust libraries to be 100% bug-free; second, even it really is correct, you always suffer from performance costs from invoking the library. There is no such thing as "performance" in scientific knowledge; indeed, a short proof is better than a long one as long as they are both correct, but they are just as useful in that they show the solution is correct.
As others have written, modern Engineering could not be done without the existence of such working solutions.
We often have the idea of "solved problem" in science, but very few of them in software development (overgeneralizing a bit, any field of technology). This is probably because science is often about "what" (what is the fastest algorithm for matrix multiplication?), "whether" (does P = NP?), while technology is often about "how" (how to implement matrix multiplication efficiently?).
Once you solve a problem in science, you solve it for good. But in technology there can always be "better" ways to solve it, and things keep evolving.