We want causal correlations. Someone decided that instead they wanted to divide food into categoried in this specific way, and then rank categories. And I don't think all of them were naive about what they were doing. I've read Merchants of Doubt, I don't give harmful industries the benefit of doubt when it comes to things like this.
12 weeks is incorrect, you can buy the same Cornish crosses that the big farms use. So they can be ready in as little as 6-7 weeks but I usually stretch it to 8 or 9; my time to process them is fixed so I might as well get a little bit more meat for my efforts.
I use a chicken tractor that is big enough to let me hold about 33 at a time.
So it’s an operation that needs to run for about half the year. If you time it right, you can work around vacations and stuff. Daily operations are actually pretty minimal in terms of time spent, but you do lose three weekends a year to process them if you don’t outsource that.
All of that to say: I’m not sure if I want to agree with your characterization. It’s less of a time commitment than you think. But there is a substantial cost to it all: capital costs are notable and the cost of feed and birds is such that you basically break even against high-end organic products for sale. You’re always going to look at the Costco chicken and wonder why you are doing it. I treat it as a “touch grass” hobby that kinda breaks even.
No real point, just excited to have something to say about this haha
It depends. My friend's dad has chickens and the meat is tough and grey-dark, very much not like the supermarket white and soft meat. Also the meat tastes of... chicken; I guess. And you can see even the bones are significantly harder (I can't snap them with my fingers like the supermarket chickens' bones). I always assumed this is because of the way they're raised, allowed to roam freely (within an enclosure, but it's a big one) and feed on scraps and everything they can forage for, in addition to grain.
What does your chickens' meat look and taste like? If it's the same as supermarket chicken then, I don't know, but if it's the other kind then it's definitely worth it. Although it takes a couple hours cooking to soften it :)
Triumphant? Victorious? magnificent, successful, proud, powerful, insert any adjective which applies to a situation where someone wanted something, and then got it.
> "And it is very hard to see how carrying out a proof automatically is "not reasoning. The same clearly does not apply to Python, because its interpreter is not an automated theorem prover; it doesn't apply to javascript because its interpreter is not an automated theorem prover"
And that does not stop Python or Javascript from being used to find solutions to e.g. an Einstein Puzzle, something a human might call "a reasoning problem". This means Prolog 'doing reasoning' must not be the thing which solves the 'reasoning problem', something else must be doing that because non-reasoning systems can do it too.
If Prolog 'doing reasoning' meant it could solve 'reasoning problems' that no other programming language could, that would be a strong reason to use Prolog, but that is not something you or the other 'reasoning' commenters have claimed or offered examples of. Clearly the word 'reasoning' has different definitions in the different sentences and that is important here because I am responding to one and youall on the other.
If 'doing reasoning' is not the thing which makes it useful for 'solving reasoning problems' - if that neither compels one to use Prolog when working to 'solve a reasoning problem', nor convinces one to avoid other languages - if the definition does not influence one's decision in any way - it's very hard to see how it is the relevant version of 'reasoning' to focus on, and what point is trying to be made by this insistence on focusing on it, except academic one-upping.
To solve an Einstein puzzle in Python et al. you have to code 1) a definition of the problem and 2) a solution that you come up with. In Prolog you only have to code a definition of the problem and then executing the definition gets to the solution.
Other languages indeed can solve problems that Prolog can, but a human programmer must code the solution, while Prolog comes built-in with a universal problem solver, SLD-Resolution, that can solve any problem a human programmer can pose to it.
I looked around for an example of this with real code and found this SO thread on programmatically solving a Zebra puzzle (same as the Einstein puzzle):
https://stackoverflow.com/questions/318888/solving-who-owns-...
There are a few proposed solutions in Python, and in Prolog. The Python solutions pull-in constraint solving libraries, encode the problem constraints and then use for-loops to iterate over the set of solutions that respect the constraints.
The Prolog solutions do not pull in any libraries and do not iterate. They declare the constraints of the problem and then execute the constraints, letting the Prolog interpreter find a solution that satisfies them.
So the difference is that Prolog can solve the problem on its own, while Python can solve it only if you hand-code the solution, which includes importing a constraint solver. Constraint solving is of course a form of reasoning, and that's how you can get Python to do reasoning: by implementing a reasoning algorithm. In Prolog you don't need to do that, because SLD-Resolution is a universal problem solver that can be applied to constraint problems, like any other problem. This is not an academic matter, as you insist that it is; it is a practical matter, of knowing how to code a universal problem solver and getting it to run on real-world hardware.
I say that solving constraints is a form of reasoning. You won't find anyone to disagree with this in the CS and symbolic AI community. While you also won't find an agreed-upon, formal definition of "reasoning", we don't need one because we've been studying reasoning since the time of Aristotle and his "Syllogisms" (literally, "Reasonings" in Greek). In the same way you won't really find an agreed-upon definition of "mathematics", but we don't need one because we've been studying maths since the time of the ancient Babylonians (at least; my memory is hazy).
You argue that what Prolog does isn't reasoning, but that's a very niche view. Not that this means you're wrong, but one reason I insist with this discussion is that your view is so unorthodox. If you're right, I'd like to know, so I can understand where I was wrong. But so far I still only see a misunderstanding of Prolog and a continued unwillingness to engage with the argument that Prolog does reasoning because it has an automated theorem prover as an interpreter.
Note that the Prolog solutions in the SO thread are a bit over-engineered for my tastes. The one in the link below is much more straightforward although it's for a simplified version of the problem. Still, it shows what I mean that you only need to define the problem and then the interpreter figures out how to solve it.
https://www.101computing.net/solving-a-zebra-puzzle-using-pr...
But I will say, when you buy chicken at the grocery store, the quality can vary. Mine has always been good.
Heh. Over here (UK and the rest of Europe I reckon) the kids love chicken thighs. Acquired tastes eh?