3 ms·
I actually agree with you in a general sense, but our own opinions don't really matter much. What matters is the opinions in the aggregate. I wish that it wasn
by steveklabnik 7y ago
I actually agree with you in a general sense, but our own opinions don't really matter much. What matters is the opinions in the aggregate.
I wish that it wasn't perceived as such, but the reality is that it is. Ignore that at your own peril.
- quotemstr 7y agoWhat peril? Why is everyone treating online outrage mobs as if they had any power or authority? Who cares if some unimportant anonymous commentator thinks a fork is aggressive?
- steveklabnik 7y agoIf you are trying to get people to use your project, understanding how those people perceive your project is step 1.
- quotemstr 7y agoAgreed. But how do we define "people"? Are your prospective users all hanging out on Reddit and Twitter? Or are these two communities, as I believe, vocal but unrepresentative slices of a much larger potential silent user base?
- steveklabnik 7y agoTotally, I think that sometimes, forks do make sense! Sometimes, you have to be aggressive, and people will find it justified. io.js is a great example of this happening and working.
- godshatter 7y agoWhy? What's the danger here? Is the original maintainer going to send someone named Vinny to break your legs if you fork a project that won't accept a security patch you need? I think you should just fork it privately, apply your patch, and move on with your life.
- steveklabnik 7y agoIf you're keeping it private, none of this applies. I'm talking about "hey that project is bad, I am now maintaining a competing project, please use it instead."
- growse 7y agoInstead of framing it as "that project is objectively bad, my one is better", why not say "my project is a fork of this project but with a bit less unsafe" and then see what the community does? Forking isn't provocative. Forking and then claiming your fork is objectively superior is.