The kinds of projects you can do solo are often trivial to clone because what makes you unique won't be raw manpower invested.
But for the example of shapez, there's a lot of added value that's not in the source code. The creator is active in the shapez discord, and there are also paid DLCs on Steam which aren't open source. So there are at least some ways to monetize and make your community loyal that are still compatible with open source.
I think "program build consultancy" is an overly cynical way to look at this particular situation. I was more than happy to pay the $10 to support the guy and not have to muck with an Electron build. /shrug
Sure? I feel like it wouldn't be unusual semantically to see a sentence like "the Foobar mountain brings in eleventy zillion dollars in tourism per year".
In this case, thinking of it as “mountain-related” income shadows the fact that your business is actually tourism, an insight which could lead you to invest in other, non-mountain-related but tourism-benefiting projects.
Why not? What if you collect large donations?
Wikimedia makes a lot of money (for itself) even with all the open-source-non-affiliated activities removed.
Your comparison is incorrect because you wrote a program whereas the guide didn't set up the trail or build infrastructure to hike on the mountains
It's a very helpful metaphor though, thanks for that. Free software is doing a ton, but there is a lot of space left unepxlored for economical reasons, surprisingly. I've seen projects refusing to document their code or clean up their APIs, leaving a high barrier to entry just to keep the consultancy running. Then there's the fact that infrastructure is never sexy, and then the whole xkcd #2347 problem where the entire world relies on one destitute retired person in their dacha to keep their lights on with a key library that everyone uses quietly.
Makes me think if there could ever be a model that implements micropayments for software library usage, a little like lambda calls or like pay-by-article models for newspapers. But the reason why that isn't feasible may be the same reason why hiking trails aren't toll roads.
They are not saying "prohibit free access" here.
• https://www.gnu.org/philosophy/selling.html.en
• https://www.gnu.org/philosophy/selling-exceptions.html
But these are not the only means to make money! To return to my mountain analogy, you could easily imagine many ways to profit from the mere existence of a mountain. You could, as I wrote, give guided tours, but you could also build water slides, build an observatory at the highest peak, or mine the mountain for precious minerals. All these have some risk, of course, of damaging the mountain itself, but they are all money-making schemes which would not occur to anyone wanting to somehow profit off the mountain exactly as it is.
Therefore, calling it “making money from FOSS” is simplistic and limits your own thinking.