Long, long ago, humans were capable of eating lots of things raw. Now, not so much. We've rounded up nine foods that you really need to cook before eating.
The earliest humans had a specialized organ whose chief purpose was to help digest cellulose (among other things): the appendix. Now that it's vestigial, certain foods that are very high in cellulose, like kale spines, need to be removed and aren't edible at all. But there are a host of reasons why some foods need to be cooked before eating, and the fact that they can't be digested is just one of them.
Click Here to see The Complete List of Foods You Should Never Eat Raw These you really shouldn’t eat at all; forget about cooking them first. If you crack open seeds and pits from fruits that contain them, the inside is soft and appears to be edible. But don’t eat it: it contains a chemical called amygdalin that can turn into — you guessed it — cyanide (who knew that so many foods contained cyanide?). Thankfully, you’d need to eat a whole lot of peach pits in order to get sick, but we wouldn’t chance it. Photo Credit: iStockPhoto/ Thinkstock
You know how sometimes older potatoes can begin to turn a funky shade of green? Yeah, you don’t want to eat that part. When potatoes get too much sunlight, a chemical called solanine can build up to toxic levels, and that’s what the green is. If consumed, it can lead to headache, fatigue, nausea, and stomach issues. Store your potatoes in a cool, dry place and you’ll avoid this problem. Photo Credit: iStockPhoto/ Thinkstock
Click Here to see The Complete List of Foods You Should Never Eat Raw Pork no longer needs to be cooked to well-done, but you should still cook it past the medium point. Pork still has the potential to carry a couple of bugs: trichinosis, a roundworm; and pork tapeworm, which can grow up to 6 feet long in the gut of a pig. If the meat is eaten undercooked, it can transmit the parasite to you, with some unpleasant side effects. These diseases largely hail from the days when pigs were allowed to eat garbage, and have largely been eradicated by modern processing. It’s still risky, though, and rare pork doesn’t taste very good, either. Photo Credit: iStockPhoto/ Thinkstock
If you were to take a few raw kidney beans off the vine and eat them, not only would they taste gross, but within a couple hours you’ll be nauseous, vomiting, and have an upset stomach. The culprit? A natural toxin called lectin. Soak the beans in water for at least five hours before cooking and you’ll be fine. Photo Credit: iStockPhoto/ Thinkstock
Click Here to see The Complete List of Foods You Should Never Eat Raw You might have heard that rhubarb is poisonous when raw, but it’s actually the leaves you should avoid at all costs. The leaves contain insanely high levels of a toxin called oxalic acid, which when consumed can cause serious kidney damage, and possibly even death. Even a small amount can make you sick, and 10 or so pounds is enough to kill you. Photo Credit: iStockPhoto/ Thinkstock
The most obvious food that needs to be cooked is meat. Aside from it being difficult for our stomachs to process a big slab of raw meat, it can also be full of parasites and bacteria that can kill, like salmonella. Other foods contain poisons that need to be cooked off. Also, don't forget that these foods tend to taste pretty bad.
Some of these foods might surprise you: yucca, also known as cassava, doesn't just taste bad raw; it can also send you to the hospital if eaten uncooked. Others, like chicken, aren't that surprising at all, but still good to know about. So read on to learn about nine foods that you shouldn't eat raw, and why.
-Dan Myers, The Daily Meal
More Content from The Daily Meal:
Follow The Daily Meal on Twitter: www.twitter.com/thedailymeal