3 ms·
> it lowers barriers to contribution Arguably this is a bad thing. Lowering the bar is not necessarily a good thing. How could it be? EDIT: Please if you down
by johnisgood 8y ago
> it lowers barriers to contribution
Arguably this is a bad thing. Lowering the bar is not necessarily a good thing. How could it be?
EDIT: Please if you down-vote, could you also provide a reason as to why lowering barriers to contribution is inherently a good thing, and why even considering the idea that it may not be, is something utterly horrible that requires a down-vote? Sure, you don't have to, just trying...
- achamayou 8y agoDealing with unnecessary build and packaging complications, often dictated by legacy constraints, is a distraction for a systems programmer and does nothing for the quality of the software itself.
- johnisgood 8y agoOK, but that means that people who are more motivated and knowledgeable (depends) will be the ones contributing, or will make up the majority of contributors. Does it not? I can see how it could be beneficial to a project.
- papaf 8y agopeople who are more motivated and knowledgeable (depends) will be the ones contributing I have contributed to projects where I am neither motivated or knowledgeable.Sometimes its enough to be annoyed by a bug or confusing behaviour.
- johnisgood 8y agoI would say that is being motivated though, just with a different motivator! :P
- achamayou 8y agoBut they will be knowledgeable in something that is only tangentially related to systems programming. You are potentially missing out on a lot of talented systems programmers who are not willing or able to put up with terrible build and packaging infra and therefore stick to another domain. As for motivation, you are also missing out on anyone who has a small contribution to make but isn’t willing to dedicate hours trawling through Makefiles. That doesn’t seem good either?
- johnisgood 8y agoI didn't say it was without downsides, I realized that there's a huge potential of losing lots of talented people who merely just don't have the patience to [...]. I don't have anything valuable to add, hopefully someone else might.
- rrdharan 8y ago"Lowering the bar" and "lowering barriers" are two very different things that you are conflating.
- johnisgood 8y agoIs it? I have seen them used in the exact same way. For example: lowering barriers to entry to a university is lowering the bar. Are they not the same thing?
- finnh 8y agoExample: A high application fee is a barrier. Lowering it does not lower the bar.
- johnisgood 8y agoDefinition: > To lower the standards of quality that are expected of or required for something "or required for something". I think it pretty much fits according to the definition, but it is usually used in terms of abilities or skills. https://idioms.thefreedictionary.com/lowering+the+bar https://idioms.thefreedictionary.com/lowering+the+bar
- Jtsummers 8y agoYou’re not parsing that correctly. To lower the standards of quality that are expected of something. Or To lower the standards of quality that are required for something. Lowering the bar is a reduction of quality. Lowering barriers is not the same thing.
- johnisgood 8y agoBy reducing the barrier to entry by, say, making the tests easier (or the use of build systems), then effectively you are reducing the quality of "applicants". Eliminate the barrier completely (get rid of the tests), and it is guaranteed that you will get many more applicants who would not be fit for whatever. Doesn't this make sense?
- nindalf 8y agoAre you not a native English speaker? I ask because most non-native speakers will accept and appreciate the correction. Only a native speaker would confidently defend their interpretation. And yet, I find it difficult to understand how a native speaker could possible misinterpret this statement.
- johnisgood 8y agoBy statement do you mean "it lowers barriers to contribution"? I just have the idea that you will get more applicants or submissions this way because anyone, without zero effort, could submit their contributions. It's the case with other package managers, too. If you take a look at modern package managers, it is filled with actual garbage, and only very few are of high quality. It seems heavily polluted, due to lowered barriers to submit them, I think. Noobs can just type in a command without having to research it or RTFM, and boom, it's there. I am not sure how people can think that this is necessarily a good thing, still. And to comment on the "native English speaker" part: If by statement you meant "it lowers barriers to contribution": https://news.ycombinator.com/item?id=19066478 https://news.ycombinator.com/item?id=19066478 I think it explains it well.
- geofft 8y agoI did not downvote, but a) if you're going to say "Arguably this is a bad thing," you should provide an argument (or, if you don't want to say that, you can say "I don't understand this, can someone please explain" instead of "How could it be") and b) on HN downvotes are a valid way to express disagreements.
- johnisgood 8y agoWhile I did not really have an argument, I thought I let someone else who may think the same come along and provide an argument. Or are we all to assume that it is actually inherently, or necessarily a good thing until proven otherwise? I understand that I could have said exactly those things to help on the matter. I am aware of down-votes being a way of expressing disagreements, and I don't expect everyone to provide a reason for doing so.