I see this a lot when people are looking for some library / framework / programming language / game engine. You keep adding requirements and assume that you can spend some additional time evaluating alternatives to make up for the longer list of requirements you have. Reality is, there are often only a few serious alternatives in the first place. Adding more and more requirements to your search is, in some way, a stubborn refusal to prioritize among those requirements. Prioritization doesn’t just mean affirming that some of your priorities are important, it means acknowledging that some of your priorities are unimportant and can be discarded.
Related is the assumption that any custom-built library you write is going to beat an existing, well-known library that doesn’t exactly match your needs. It’s easy to come up with a list of problems with existing libraries, but your theoretical custom-built library can be perfect, because you’re not imagining that it has any serious bugs or design flaws. You end up building your own solution and, in the process, rediscover why the existing library was built the way it is.
Related is the assumption that any custom-built library you write is going to beat an existing, well-known library that doesn’t exactly match your needs. It’s easy to come up with a list of problems with existing libraries, but your theoretical custom-built library can be perfect, because you’re not imagining that it has any serious bugs or design flaws. You end up building your own solution and, in the process, rediscover why the existing library was built the way it is.