4 ms·
I don't disagree, but good vs bad error messages can be the different between a project that people love and contribute to and a project that people find frustr
by solidasparagus 7y ago
I don't disagree, but good vs bad error messages can be the different between a project that people love and contribute to and a project that people find frustrating and bombard with issues.
Keras is great about error message[1] and it's part of what makes Keras beloved (and heavily contributed to).
[1] https://blog.keras.io/user-experience-design-for-apis.html https://blog.keras.io/user-experience-design-for-apis.html
- leeoniya 7y agohonestly, i already maintain too many open source projects (and quickly resolve bug reports) to be worried about people not using more of my free work. i write open source code primarily for myself. doing anything i dont consider critical takes the joy out of doing it. if people want features, they can fork and contribute code and then maintain that code, too...forever. of course, once you shift that burden to them, suddenly no one wants to get involved. sorry for putting it this bluntly but it's the truth. i am one human, with a 9-5 and a life outside of coding. people seem to feel entitled to opinions on free open-source projects having contributed little-to-nothing.
- journalctl 7y agoI’m pretty sure the parent was just making an honest suggestion that wasn’t meant to attack or hurt you. And why post on HN if you aren’t willing to listen to others’ suggestions/criticisms of your work?
- leeoniya 7y agolook, i get it. i'm not offended. but i want to keep lib size minimal and adding validation and error messages will bloat it. a lot. i typically add them (or update the docs) once users encounter problems and open Github issues (reactively). doing it proactively is a waste of time (for me). i accept the criticism. i just don't have the necessary free cycles to address it.