|
|
|
|
|
by wat10000
127 days ago
|
|
I can't tell if this is satire or not. I fear that it's not. "If you make your project public, it means you want and expect people to use it. You could at least write some documentation, so I don't waste my time and then find out, days later, it isn't capable of what I need or I simply don't know how to use it." WTF? If I make it public it's because I think other people might like to see it. That runs the gamut from "this is a production-ready project that solves a major problem" to "this is useless but shows some interesting techniques you might like to learn from." If you spent days fiddling with an undocumented project that turned out not to do what you need, I'm not the one who wasted your time. That would be you. If you want to limit yourself to only looking at high-quality projects with documentations and active bug trackers and PR reviewers, go for it. That's probably a good move! But putting some source files on a web server does not imply any further obligation, in those areas or any other. |
|
I know what I am and I know the degree to which people suck. Don't walk into abuse teeth first and then make a surprise Pikachu face about it.