4 ms·

OP having a lesson about flip-side of open source software. I have never written JavaScript or NativeScript but it is very uncomfortable to read a aggressive co

OP having a lesson about flip-side of open source software. I have never written JavaScript or NativeScript but it is very uncomfortable to read a aggressive commentary about an OSS. > 2. Documentation is ridiculous > They are behind with the docs for years. They always promise that the next version’s documentation will be really finished and will be awesome and contain everything. So what? That's your responsibility to start a project with an open source framework that doesn't even have a proper documentation, you're completely free to not to use or if it is bothering you, help them. > 4. Arrogant communication > Go to their Slack channel and ask them about anything I mention above. They’ll cut you out with some trendy BS like: > "You are too negative, I can’t help” I can clearly see the reason why. > 5. There’s no support at all Yeah, i'm pretty sure that's how not open source works.

isochronous 6y ago
Jesus, dude, OSS is not some kind of holy grail that renders it immune from all criticism, much less valid criticism. 1. I agree about the "you're free not to use it" line, but I frequently find that documentation can seem comprehensive when you're evaluating something, but as soon as you get deeper into the weeds, that's when the shortcomings reveal themselves. And telling someone to "help them" when they themselves are looking for documentation to get help? That's just laughable. I sure as heck wouldn't want someone who can't get my product to work to be submitting documentation PRs. 2. This is just snide. Refusing to help someone because they're expressing frustration is simply spiteful. You have no more information than the rest of us about what was actually asked, so implying that the author "had it coming" seems uncalled for. 3. Then you're not very familiar with the OSS economy, are you? There are frequently paid support plans available for major OSS projects.
- yagizdegirmenci 6y ago
  > And telling someone to "help them" when they themselves are looking for documentation to get help? That's just laughable I'm telling exactly the same thing, if you are not comfortable with reading the source code to understand something, then you shouldn't be starting with a project that doesn't even have a documentation. > 3. Then you're not very familiar with the OSS economy, are you? There are frequently paid support plans available for major OSS projects. This is not right, you are talking about mainstream projects, except from people getting paid to contribute open source (like people working on Kubernetes, Firecracker, Gvisor, Bottlerocket, Podman, Red Hat's stuff, Linux Foundation etc), they are doing "free work". Yes, author is completely free to do whatever criticism they want, but for a project that doesn't even have 2 donators, author has a too offensive language and basically expecting too much.

isochronous 6y ago

Jesus, dude, OSS is not some kind of holy grail that renders it immune from all criticism, much less valid criticism. 1. I agree about the "you're free not to use it" line, but I frequently find that documentation can seem comprehensive when you're evaluating something, but as soon as you get deeper into the weeds, that's when the shortcomings reveal themselves. And telling someone to "help them" when they themselves are looking for documentation to get help? That's just laughable. I sure as heck wouldn't want someone who can't get my product to work to be submitting documentation PRs. 2. This is just snide. Refusing to help someone because they're expressing frustration is simply spiteful. You have no more information than the rest of us about what was actually asked, so implying that the author "had it coming" seems uncalled for. 3. Then you're not very familiar with the OSS economy, are you? There are frequently paid support plans available for major OSS projects.

yagizdegirmenci 6y ago
> And telling someone to "help them" when they themselves are looking for documentation to get help? That's just laughable I'm telling exactly the same thing, if you are not comfortable with reading the source code to understand something, then you shouldn't be starting with a project that doesn't even have a documentation. > 3. Then you're not very familiar with the OSS economy, are you? There are frequently paid support plans available for major OSS projects. This is not right, you are talking about mainstream projects, except from people getting paid to contribute open source (like people working on Kubernetes, Firecracker, Gvisor, Bottlerocket, Podman, Red Hat's stuff, Linux Foundation etc), they are doing "free work". Yes, author is completely free to do whatever criticism they want, but for a project that doesn't even have 2 donators, author has a too offensive language and basically expecting too much.