21–30 of 30 posts
[flagged]
> Side note: I’ve repeatedly noticed this same self-righteousness advertised by similar autistic / ADHD-coded people online, particularly in the software dev space, and particularly amongst what I’d call the bluesky / mastodon set.
Ah, this explains a lot about your views
Earlier quoted context omitted.
If you think what you're doing is good for anyone to do, it's only logical to nudge people around you to do it.
Sure. So how would you feel about a Christian nudging you to stop taking the lord’s name in vain because they believe it’s “good for anyone to do”?
What a weird hill to choose to die on. I wasn't even aware of the trend, but I love it now that I'm aware of it; it makes total sense. If you're a prescriptivist, then open-source should be hyphenated for the same reason full-time, user-friendly, long-term, etc. are. That's how English works. You don't make the rules, and neither does OSI. If you're a descriptivist, then why are is OSI getting a monopoly on everyone'…
I also get the sense that the author has an inherently negative view of non-OSI-approved "source available" licenses -- and in particular the Business Source License, which he uses as a counterexample twice.
Yet, OSI cofounder Bruce Perens helped improve that license and specifically said "I feel it’s worthy of my endorsement. The new BSL will be a good way for developers to get paid while eventually making their works Open Source." [1]
Why do so many vocal people in the Open Source world have a much more extreme worldview than even an OSI cofounder?
[1] https://web.archive.org/web/20250629110730/https://perens.co...
Earlier quoted context omitted.
Sure. So how would you feel about a Christian nudging you to stop taking the lord’s name in vain because they believe it’s “good for anyone to do”?
I'd be annoyed and try to get them out of my space or leave myself. Is that bad?
What a weird hill to choose to die on. I wasn't even aware of the trend, but I love it now that I'm aware of it; it makes total sense. If you're a prescriptivist, then open-source should be hyphenated for the same reason full-time, user-friendly, long-term, etc. are. That's how English works. You don't make the rules, and neither does OSI. If you're a descriptivist, then why are is OSI getting a monopoly on everyone'…
Totally agreed. They don't have a trademark, and their superfans have no right to tell people how to capitalize or punctuate the term. I also get the sense that the author has an inherently negative view of non-OSI-approved "source available" licenses -- and in particular the Business Source License, which he uses as a counterexample twice. Yet, OSI cofounder Bruce Perens helped improve that license and specifically…
I've previously worked at a company using an "open source" license (Elastic, with the ELv2) and have enjoyed having to explain the difference to folks between what it meant to be "open source" vs "Open Source", and the fact that a lot of folks generally don't understand the difference and some of the nuance. Mentioning the BuSL was because it's something a lot more folks may be aware of, i.e. given Hashicorp's recent relicense (as with other companies in recent years)
Sustainability is hard, and having different ways to describe this is good! But it's a lot harder when people don't understand why something calling itself "open source" when it's "but you can't run it if you're a company" is bad
Earlier quoted context omitted.
Totally agreed. They don't have a trademark, and their superfans have no right to tell people how to capitalize or punctuate the term. I also get the sense that the author has an inherently negative view of non-OSI-approved "source available" licenses -- and in particular the Business Source License, which he uses as a counterexample twice. Yet, OSI cofounder Bruce Perens helped improve that license and specifically…
I personally prefer Free Software (FSF-approved) or Open Source (OSI-approved) licenses, but I also agree that there is a place for other licenses. It's better that there's space for kinda-open, rather than it being open vs completely closed repositories. I've previously worked at a company using an "open source" license (Elastic, with the ELv2) and have enjoyed having to explain the difference to folks between what…
That's good to hear, sincere apologies for assuming otherwise. There are a lot of folks on HN who take a much more extreme view there, and I seem to have incorrectly conflated them in the "open source" vs "Open Source" debate.
> having to explain the difference to folks between what it meant to be "open source" vs "Open Source", and the fact that a lot of folks generally don't understand the difference and some of the nuance
This speaks to the core naming problem though: the original OSI folks should have picked a better term! They thought "Free Software" wasn't a good term in part due to the gratis vs freedom confusion (totally agreed here), and yet they picked another equally-confusing term to use instead, that had a pre-existing generic meaning which wasn't related to specific license terms in any way.
The derailment of free software to a profit making exercise. As opposed to the sharing of software written by entities that will use the software,, and thus write it for themselves.
Apparently, there is only for-sale products, no entity that would use software would ever write it. And even if they did, they would never share it.
The purpose of life, the universe and everything: shareholder returns, obviously...
What a weird hill to choose to die on. I wasn't even aware of the trend, but I love it now that I'm aware of it; it makes total sense. If you're a prescriptivist, then open-source should be hyphenated for the same reason full-time, user-friendly, long-term, etc. are. That's how English works. You don't make the rules, and neither does OSI. If you're a descriptivist, then why are is OSI getting a monopoly on everyone'…
Totally agreed. They don't have a trademark, and their superfans have no right to tell people how to capitalize or punctuate the term. I also get the sense that the author has an inherently negative view of non-OSI-approved "source available" licenses -- and in particular the Business Source License, which he uses as a counterexample twice. Yet, OSI cofounder Bruce Perens helped improve that license and specifically…
In my experience talking with many such people over decades... it's usually some type of personality disorder. I quit FOSS because of how prevalent this egotistical dogmatism persona is.
Besides the users that never stop complaining and love to make absurd demands of unpaid volunteers, a very depressingly-large number of other developers you end up working with are so self-absorbed and uninterested in actually getting along with other people that their only means of discussion is always about how everyone else is wrong and there can be no other valid opinions.