Your comment gives the impression that you think open source software is only developed by unpaid hobbyists. This not true, this is quite an outdated view. Many things are worked on by developers paid full time.
And that people are mostly interested in algorithmically challenging stuff, which I don't think is the case.
Accessibility does need improvement. It seems severely lacking. Although your link makes it look like it's not that bad actually, I would have expected worse.
This makes me wonder, is there analysis of the syntax and if so can't it pick the lightest implementation? I see how light dillo is on the same page as chrome and I don't know why a web browser of the caliber of chrome does so much worse than a browser worked by a handful of people.
You don't know that. I don't know about you (and whatever you wrote possibly tells more about yourself than anyone else), but I prefer my positions strong and based on reality, not based on lies (to myself included).
And the environment is far from being the only concern.
You are attacking a straw man. For you, being against GenAI, simply because it happens to be against your beliefs, is necessarily irrational. Please don't do this.
> I prefer my positions strong and based on reality, not based on lies (to myself included).
Then you would be the exception, not the rule.
And if you find yourself attached to any ideology, then you are also wrong about yourself. Subscribing to any ideology is by definition lying to yourself.
Being able to place yourself into the shoes of others is something evolution spent 1000s of generations hardwiring into us, I'm very confident in my reading of the situation.
> Having beliefs, principles or values is not lying to oneself.
The lie is that you adopted "beliefs, principles or values" which cannot ever serve your interests, you have subsumed yourself into something that cannot ever reciprocate. Ideology by definition even alters your perceived interests, a more potent subversion cannot be had (up to now, with potential involuntary neural interfaces on the horizon).
> Citation needed
I will not be providing one, but that you believe one is required is telling. There is no further point to this discussion.
> But then comes somebody and decides to just flush your well curated history down the toilet (=delete it and start somewhere else from scratch) and then all the valuable metadata stored in the history is lost.
How does this happen? I haven't run into this.
> Maybe consider putting your energy into a good documentation inside the repository
I'd say both are valuable.
I use git log and git blame to try to understand how a piece of code came to be. This has saved me a few times.
Recently, I was about to replace something strange to something way more obvious to fix a rendering issue (like, in some HTML, an SVG file was displayed by pasting its content into the HTML directly, and I was about to use an img tag to display it instead), but the git log told me that previously, the SVG was indeed displayed using an img tag and the change was made to fix the issue that the links in the SVG were not working. I would have inadvertently reverted a fix and caused a regression.
I would have missed the reason a code was like this with a big "work" end of the day commit.
It would have been better if the person had commented their change with something like "I know, looks weird, but we need this for the SVG to be interactive" (and I told them btw), but it's easy to not notice a situation where a comment is warranted. When you've spent a couple of hours in some code, your change can end up feeling obvious to you.
The code history is one of the strategies to understand the code, and meaningful commits help with this.
> Haven't open source projects done the rug pull too? Can't they relicense new code going forward?
They can, if the original license is permissive, or if there was a CLA. They can't for significant contributions under a copyleft license that was not done under a CLA. Something to consider when contributing to a project that uses a CLA or a permissive license.
> I get that there is an important distinction but from an adoption and evangelism standpoint it seems like an unnecessary crusade to push them away.
Depends on your goals. If source available misses the point anyway, adoption doesn't help, the message risks being blurred, and therefore you should push back.
> Open source isn't really about the license, and it's also not even really about the source; open source is a philosophy centering open development and collaboration.
Not really. A project under an open source license which doesn't accept contributions is still open source.
It is totally about the license and the source code availability.
There are interesting things to say about the various development models, and those common in the open source world, but the open source aspect and the development model aspect should not be mixed.
I'm not actually claiming that an open source license that doesn't accept contributions is not open source. See my post where I say it's not a bright line.
But claiming open source is totally about the source and the license completely erases the diverse and vibrant community that has formed around open source over the past 40 years. The license is simply putting the community ethos into a legal document. The source being open represents a meeting place which focuses and collects the community. But the real power of open source is the human element that drives it, and the development philosophy they hold, not the source code.
Linux for instance wouldn't nearly be the powerhouse it is if it were merely "source available". You're really misunderstanding the power of open source if you think it's all about the code, and not the development model.
The human aspects, the diverse and vibrant community that has formed around open source over the past 40 years are key, I just think that we should cleanly separate the concepts.
A piece of software is open source if and only if it's released under an open source license. It's necessary and sufficient. Also "source available" is necessary but not sufficient.
Then we can and should talk about how and why open source and free software appeared, and the other social aspects around open source and free software and how they are crucial.
I'm not stating that the whole thing is not important (clearly, it is),
it's just that keeping the concepts separate and clean helps communicating clearly.
My stance is already mostly not technical actually. I would push for free software and the human rights it embodies way more than open source despite open source and free software concerning mostly the same actual software. The tools (licenses) are mostly the same, but the intent and the approach can be very different.
Even the open source definition and the free software definitions are tools. They must remain clear and simple to be useful and powerful.
If you mix everything, we can talk about nothing.
There are many ways to develop open source software, including alone from a garage by throwing the source code out of the window without never looking outside. If you make the community aspect part of the open source definition, you break this.
Accessibility does need improvement. It seems severely lacking. Although your link makes it look like it's not that bad actually, I would have expected worse.
reply