There are lots of cases where projects are so successful and get so complex that the best step for the maintainer who created it is to step down from making the

There are lots of cases where projects are so successful and get so complex that the best step for the maintainer who created it is to step down from making the final technical decisions. I can imagine that it’s super hard to build a super fast web server that is also memory safe. It seems like the good thing was to focus on speed first, but at some point the server became somewhat of a standard, and at that point memory unsafety can create huge damage and has to become the priority. In this specific case I would have added a benchmark to the CI and not accept pull requests with regressions of speed. That would have put the pressure on the contributors to find solutions that improve safety without compromising for speed.