What exactly does "open" mean when used as a qualifier for "source"?
The fact is that your claim "“open source” consists of two words which have meaning, but somehow doesn’t mean ==>that<== when combined into one phrase" is simply false, as there is no "that".
> Same with free software, in a way.
This is a much more supportable argument, but note the change in wording: "free software" is not the same as "free source". The latter suggests that one doesn't have to pay for the source, but says nothing about what one can do with the source or one's rights to software built from that source.
As for "free [as in freedom] software", I think there would have been less contention if RMS/FSF had called it "freed software" or "liberated software", and it would have been more consistent with their stated goals.
> Programmers really are terrible at naming things.
This is silly sophism based on one anecdote that you didn't even get right. Naming things well is hard, and names in software have conditions that don't exist in more casual circumstances. The reality is that good programmers put a lot of effort into choosing names and generally are better at it than the population at large.
You're close: they should have called it "freedom software". Which they wanted to, but couldn't, because it was trademarked. Source: I e-mailed richard stallman to ask why they didn't, he replied.
You're welcome to think what you want, but I've had to explain to enough juniors enough times what "open" actually means, so I know what people without any preconceived notions think it means, vs what experts on HN associate with the word after decades in the industry.
People who are new to the profession entirely, think that "open" means "you can look inside." Source: my life, unfortunately.
> ... that you didn't even get right.
FYI: this style of conversation won't get anyone to listen to you. And FWIW I was referencing the quip which I'm sure your familiar with. It was tongue in cheek.
> The reality is that good programmers put a lot of effort into choosing names and generally are better at it than the population at large.
> I've had to explain to enough juniors enough times what "open" actually means, so I know what people without any preconceived notions think it means, vs what experts on HN associate with the word after decades in the industry.
This is not relevant--it addresses a strawman and deflects from the actual claim you made and that I disputed.
> FYI: this style of conversation won't get anyone to listen to you.
Projection. I will in fact cease to respond to you.
> ... isn't that a No True Scotsman?
Obviously not. Failing to understand the difference between "real", "actual", "true" etc. which are the essence of the fallacy and valid qualifiers like "good" shows a fundamental failure to understand the point of the fallacy.
Even without a specific definition for "open source", I wouldn't consider source code with a restrictive license that doesn't allow you to do much with it to be "open".
I don't think this is a case of programmers being bad at things (although I get that you said that as a joke), I think it's much worse than that: This is some kind of weird mind-over-matter "if we believe it hard enough it'll come true" thing. Sort of an "if we beat everyone who says the emperor has no clothes, we can redefine 'clothes' to include 'the emperor's birthday suit'". Note that these people who are downvoting anyone who dares to say that "open source" isn't synonymous with the OSI definition never concede an inch to the notion that the words have a common-sense meaning and the OSI didn't invent the term (provable via internet archive). Because it's not about being right it's about changing reality to match what they wish were true.
* If a country doesn't have "closed borders" then many foreigners can visit if they follow certain rules around visas, purpose, and length of stay. If instead anyone can enter and live there with minimal restrictions we say it has "open borders".
* If a journal isn't "closed access" it is free to read. If you additionally have permissions to redistribute, reuse, etc then it's "open access".
* If an organization doesn't practice "closed meetings" then outsiders can attend meetings to observe. If it additionally provides advance notice, allows public attendance without permission, and records or publishes minutes, then it has “open meetings.”
* A club that doesn't have "closed membership" is open to admitting members. Anyone can join provided they meet relevant criteria (if any) then it's "open membership".
Who says it isn't? "closed source" doesn't have a formal definition, but can be arbitrarily defined as the antonym of open source, and when people use the term that's usually what they mean.
And that has nothing to do with whether someone can be "blamed" for ignoring the actual meaning of a term with a formal definition.
> If you are still relying on docker, it is time to migrate.
I did work for a client recently where they were using Podman Desktop and developers are using Macbooks (Mx series).
They tried to run an amd64 image on their machine. When building a certain Docker image they had it was segfaulting with a really generic error and it wasn't specific to a RUN command because if you keep commenting out the next one, it would appear on the next one. The stack trace was related to Podman Compose's code base.
Turns out it's a verified bug with Podman with an open issue on GitHub that's affecting a lot of people.
I've been using Docker for 10 years with Docker Engine, Compose, Desktop, Toolbox, etc. and never once have I seen a single segfault, not even once.
You know what's interesting? It worked perfectly with Docker Desktop. Literally install Docker Desktop, build it and run it. Zero issues and up and running in 10 minutes.
That company got to pay me for a few hours of debugging and now they are happily paying clients for Docker Desktop because the cost for the team license is so low that having things "just work" for everyone is a lot cheaper than constant struggles and paying people to identify problems.
Docker Desktop is really robust, it's a dependable tool and absolutely worth using. It's also free until you're mega successful and are generating 8 figures of revenue.
Shouldn't be using podman compose. It's flimsy and doesn't work very well, and I'm pretty sure it doesn't have Red Hat's direct support.
Instead, activate Podman's Docker API compatibility socket, and simply set your `DOCKER_HOST` env var to that, and use your general docker client commands such as `docker`, `docker compose` and anything else that uses the Docker API. There are very few things that don't work with this, and the few things that don't are advanced setups.
For production workloads, you can use systemd socket activation to avoid most of the network issues. The caddy demo I've linked below explains more about the issues it would solve.
HN 15 years ago wasnt technical, it never was. HN is about startup business and sometimes a tech toy like whatever JS frontend is hyped this week.
The discussions are shallow and pointless, lots of actors arguing in bad faith and lots of commercial hype, lately mostly around AI to the point that the site is barely interesting for the tech-curious.
And then there's dang's moderation where he deletes comments or requires users to remove comments themselves to avoid being banned.
Github alone has +4k NES emulator projects: https://github.com/search?q=nes%20emulator&type=repositories
This is more like "wow, it can quote training data".