Determining quality requires you to do something that seemingly very few people actually resort to doing - reading code.
This was my bottom line for deciding to write and maintain my own functional programming library over another library. It's tough to find quality nowadays.
I appreciate your article because it gives such a holistic and realistic take on the state of how we choose quality and what quality really means. At the end of the day, it comes down to the code. In my experience, tests have also helped in determining the quality of a library.
Another benefit of no dependencies - it is really easy to ship your stuff in both browser and common JS node environments. Also less tooling = faster development cycles
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This was my bottom line for deciding to write and maintain my own functional programming library over another library. It's tough to find quality nowadays.
I appreciate your article because it gives such a holistic and realistic take on the state of how we choose quality and what quality really means. At the end of the day, it comes down to the code. In my experience, tests have also helped in determining the quality of a library.
Another benefit of no dependencies - it is really easy to ship your stuff in both browser and common JS node environments. Also less tooling = faster development cycles