"Like I have time to read the code of every project before I decide to use it."
I can only wonder how you make your decisions on what projects (binaries?) to use.
About pages, Google searches for x vs y, blog posts, forum comments, etc. Am I on the right track?
The bigger question is why you are even evaluating some new project in the first instance. Is there something wrong with the project you are using now? If so, can you articulate it?
Perhaps a user's intended use of a project is relevant.
As one example, consider the case where the user intends to compile and if necessary modify the code, and wants to know that this is a viable option, e.g. if something breaks. In that case does it make sense for the user to read the code?
This user might ask "Is the sbase code easier to work with than the busybox code?"
Another user might intend to rely on others to do compilation and modification (e.g., if something breaks) and then make binaries available.
Is it possible these two users might evaluate a project differently?
I can only wonder how you make your decisions on what projects (binaries?) to use.
About pages, Google searches for x vs y, blog posts, forum comments, etc. Am I on the right track?
The bigger question is why you are even evaluating some new project in the first instance. Is there something wrong with the project you are using now? If so, can you articulate it?
Perhaps a user's intended use of a project is relevant.
As one example, consider the case where the user intends to compile and if necessary modify the code, and wants to know that this is a viable option, e.g. if something breaks. In that case does it make sense for the user to read the code?
This user might ask "Is the sbase code easier to work with than the busybox code?"
Another user might intend to rely on others to do compilation and modification (e.g., if something breaks) and then make binaries available.
Is it possible these two users might evaluate a project differently?