24 ms·
While I agree with the overall decision, this hurt to read: > SInce it's closed-source, none of that matters to me. But if it was open, folks would want to gra
by remram 6y ago
While I agree with the overall decision, this hurt to read:
> SInce it's closed-source, none of that matters to me. But if it was open, folks would want to grab it to use in their own projects. I'd feel a certain responsibility to make sure that it works well, or at least to make sure that its shortcomings are well-documented. And I don't want that responsibility right now.
I see this argument over and over. I see it in academia as an excuse not to share code and data. "I haven't cleaned it", "it might not work for you". *I* will decide if it fits *my needs*, and if it doesn't I don't see how it's your fault. Code is better than no code, I always have the option of not using it.
- drenvuk 6y agoyeah it's a pretty weak argument. The first one - keeping people from ripping it off without attribution - is stronger regardless of its selfish bent.
- souldeux 6y agoit's a weak argument until you start getting pull requests, emails, passive-aggressive reddit posts, etc. etc. etc
- drenvuk 6y agojust turn off your internet already if you can't ignore people.
- UncleMeat 6y agoSo turning off your internet is an appropriate response, but making your projects closed source isn't?
- drenvuk 6y agoHow the hell did you reach that conclusion from what I wrote in the context of this thread? I'm honestly curious.
- UncleMeat 6y agoI don't like having people call me rude things on the internet. One way I can mitigate this is by not making my code OSS, which leads some small percentage of assholes to send really nasty messages when the code doesn't do what they want. The context for this thread is whether this is an acceptable reason for keeping source closed. It seems from context that you don't believe this is an acceptable reason. You also say that if I can't ignore people that I should turn off my internet, which makes me think that you believe this is an acceptable response. Thus, I believe that you believe that turning off the internet is a reasonable response and closing my source isn't.
- drenvuk 6y agoI can understand where you're coming from. My comment was meant to be hyperbole since I think if you're unable to ignore people online you should really just turn off your internet because it's really easy to ignore people online. I did not mean that you must make your code open source. I don't really care either way about that.
- nharada 6y agoYou (and many others) might have this viewpoint, but it's the loud minority that causes the pain. Even with the small amount of open source software I've maintained I've gotten all kinds of angry emails and completely useless "bug reports" with no information. It gets exhausting after a while, and I agree that it's hard to just say "I don't care at all" when it happens. At minimum it's a bad look for you professionally if you never actually help maintain your open source software.
- remram 6y agoYeah "just ignore them" is easy for me to say, but not that easy to do. I myself get plenty of those "tell me how I get started with X" emails to which I can't bring myself to reply "start with the docs". And I'm sure he already gets plenty of those support requests on account of his programming tips and courses alone...
- Cu3PO42 6y agoThis is a very reasonable position on your part. Unfortunately there are many people who don't share the sentiment. I've personally had people bug me again and again via mail, IRC, and Twitter DMs over a relatively small project that I had abandoned/wasn't able/willing to maintain anymore. Sure, I can just go ahead and ignore those people or send them a standard response, but I still found it to be mildly exhausting. I can't really blame someone for wanting to avoid that.
- thinkmassive 6y agoIt seems like a premature optimization, similar to choosing a proprietary source available license from the start because you’re worried about Amazon stealing your customers. Having aspirations about your project becoming a victim of its own success is good. Overselling your own success before it’s caused you a single issue is probably not good.
- excerionsforte 6y agoAn acceptable reason for not sharing code is because you don't want to at this time, which may very well be never which is just fine. There's no need to share your personal code especially if you do not feel proud about sharing it. Other situations like research, typically need the same materials to do verification of that work.
- remram 6y agoI agree that you don't have to release anything, and I won't call you out for it. If you write a blog post about it though, I might participate in the discussion and examine your arguments. Of course the problem of research is slightly different, since you have a claim, are trying to be "peer reviewed", and possibly were funded by public money.
- hu3 6y agoUnfortunately some people have no respect for open source maintainers time and do open issues with little to no context. Take a look at the issues of any popular Github project to see this phenomenon exacerbated. Coincidentally I stumbled upon an example today while randomly browsing Github projects. A project with 9k stars and someone opens an issue basically saying: "commands do not work": https://github.com/walkor/Workerman/issues/611 https://github.com/walkor/Workerman/issues/611 I don't mean to do finger pointing at this person. It's a common behaviour. For maintainers it's exhausting to pursue each and every issue, asking for context. And if you don't keep a tight leash on them or use a bot they just pile up to hundreds of issues.
- remram 6y agoNote that I am not saying anyone should maintain anything. Disable the issue tracker if you want. I don't demand that you respond to any communication about it or do anything further.
- DoreenMichele 6y agoI have spent a lot of years getting healthier via diet and lifestyle with an incurable and deadly condition. You would think people would welcome alternatives, given that it's incurable and deadly. You would think diet and lifestyle approaches would be the most conservative thing you could do because you have to eat and live anyway, so better to be more informed about how to do that well in the face of this. It was an amazing amount of ugly drama to try to talk to others with my condition about what I do and what I think about why it probably works. And then people would take very conservative bits of advice that were the most well established and screw them up to an amazing degree. One example: Coconut oil is a very well established beneficial supplement for my condition that is medically recommended and this is common knowledge for the CF community. It also tends to cause diarrhea. So "on my advice", someone began giving their toddler like a freaking tablespoon of coconut oil per day -- which is insane amounts to give -- and the result was very extreme amounts of diarrhea that couldn't be contained by a diaper and resulted in the floor needing to be mopped (like every single day until she finally said something to me and I was like "That's waaaay too much coconut oil to give"). So, ultimately, I left all the lists and I still write about what I do for my health, but I've worked hard at figuring out how to talk about things to a lay audience knowing that some of them can manage to do amazingly stupid and harmful things with the most conservative suggestions. And I mostly don't have an audience for that kind of writing and I'm okay with that. Go have your dumpster fire elsewhere and don't try to pin the blame on me, thanks. Code no doubt has some people like that. And there's a crazy amount of built in assumptions that the original author will know but may not know he "needs" to document and spell out explicitly so some random internet stranger doesn't create some dumpster fire and claim it's someone else's fault because "no one told me...!" And no amount of "use at your own risk" type language is enough to protect you from crazies who want something for free, aren't competent enough to effectively deploy it and now think that freebie owes them like they paid good money and it came with a warranty.
- remram 6y agoPeople might do that anyway, see how you use React components on your blog and replicate it on their own, doing it wrong and making their webpages take minutes to load. See your animated sparkles, and replicate the effect over their whole pages. They can do that without your code. If you want to make absolutely sure the "crazies" don't get any bad ideas from you, the only way is to not publish anything at all.
- aparks517 6y agoThat seems like a reasonable attitude to me. You might be surprised to learn that not everyone shares it, though. My personal experience is that my paid customers have been much friendlier and less demanding than users of things I've put out for free. That's not a problem in and of itself: sometimes demanding users is just what I need to sharpen up myself and what I'm building. Having noticed this, though, I've tried to be more thoughtful about what I put out, in what format, and under what terms. All that to say: I sympathize with both points of view.