Personally, I get pissed when companies misuse "open source" because without open source, I probably wouldn't be a developer in the first place. Just call things what they are, and leave existing terminology alone. Defending "open source" is defending the opportunity for others who were in the same situation as myself in the past.
Otherwise we'll quickly see more of what already started today, companies calling things "open source" in their marketing material but "proprietary" in their legal agreements, and no one will be better off if that's accepted.
In this case it seems like the person who submitted it to HN just used an incorrect title, so not that bad in the grand scheme of things.
My reply was more directed towards the "Why is everyone in here with pitchforks?" in a general sense, as it wouldn't have been the first time I read about someone not understanding why people who do "open source" would like the existing meaning to remain.
Personally, I get pissed when companies misuse "open source" because without open source, I probably wouldn't be a developer in the first place. Just call things what they are, and leave existing terminology alone. Defending "open source" is defending the opportunity for others who were in the same situation as myself in the past.
Otherwise we'll quickly see more of what already started today, companies calling things "open source" in their marketing material but "proprietary" in their legal agreements, and no one will be better off if that's accepted.