I like some family recipes from India: if you get a list of ingredients up front at all, no amounts will be specified. And in the middle you’ll see “add the milk” when no milk had appeared in the recipe up to that point.
I like some family recipes from India: if you get a list of ingredients up front at all, no amounts will be specified. And in the middle you’ll see “add the milk” when no milk had appeared in the recipe up to that point.
Eventually, he insisted on watching his mother make the dish.
Only for her to use limes. "Aha!" he said. "Indian Lemons" she replied. :-)
He used as an analogy how you can go to <fancy restaurant>, taste something amazing, and ask for and get the recipe. Yet even though you could make it yourself, you'll still visit the restaurant because they have the skills and practice to make it more easily than you could.
By analogy, he argued, even if you release under an open source license, you'll still get people hiring your services because that's more effective.
Someone in the audience objected. He pointed out that he had worked at <fancy restaurant>, that the recipes deliberately omitted detail, and that staff had to sign an NDA - it was nothing like "open source".
I already had my doubts about Raymond's understanding of things. That was the final nail.
But these people also still go to the pub to drink them on a night out or buy them in a can from time to time. The truth is that it's actually a lot of hassle to do homebrew well so that it tastes consistently good, and even ignoring the expensive equipment my friend has, he still probably pays more per pint to brew his own than just buying it pre-made. Obviously, he does both because he enjoys the process.
People also eat out a restaurants even though most are able to cook their own meals that are just as good, if not better.
It's not just about the food (or beer). It's also about convenience, enjoying the setting, etc.