AI finding vulnerabilities in open source software is going to make it super unpleasant for a time. I expect there to be a shift back to closed source until we get through that period.
Yes, different feed, cow breeds, etc are all going to influence taste. You also need to identify the path that the low-pasteurization milk goes through to see if it has anything that will adjust the taste. My father's professor was able to control the variables such that it was the same milk, no contaminates, etc.
There is no taste difference between raw and pasteurized milk. The taste comes from the container. If you have both in glass, there is no discernible difference. My father is a dairy farmer and bet his professor (many years ago) that he could taste the difference. The professor setup a blind taste test where he gave my father pasteurized and raw milk in glass cups. There was no difference.
"Nutritional value" is a very ambiguous. It's only in what you measured. Raw milk advocates are going to value things like bacteria and if proteins were changed. Pasteurization by definition is going to kill the bacteria and change the protein structure. The main benefit for pasteurization is that it makes milk a commodity. You can have unsanitary farms with high bacteria counts that don't make people sick. This is both good and bad. Good because it means more milk available with less disease. Bad because our bodies are complex and some bacteria is healthy.
My recommendation is that if someone wants to consume raw milk, they should have a personal relationship with the dairy.
DevOps is dead because it's run by a bunch of ops people who don't know how to do dev and a bunch of dev people who don't know how to do ops. The only tooling problem is that a bunch of companies created "DevOps tools" that then get dictated to use: K8s, terraform, etc. The only way this works is if you build the application to fit within those frameworks. Writing an indexer that is massively parallel and is mainly constrained by CPU/Memory. Instead, you have devs building something that gets thrown over the fence to a devops team that then containerizes it and throw it on K8s. What happens if the application requires lots of IOPS or network bandwidth? K8s doesn't schedule applications that way. "Oh you can customize the scheduler to take that into account". 2 years later, it's still not "customized" because they are ops people who don't know how to code. If you do customize it, the API is going to change in a few months which will break when you upgrade.
They are attributing malice/greed to what is more likely just incompetence compounded by inflation. The employees most likely haven't updated the pricing on the shelves. If you have ever been in a DG or DT, you can see that the inventory is generally a mess and just put everywhere. There is one or two people up at the front. They don't have as many people stocking shelves as a grocery store to keep the inventory in order.
This is the most common myths about homeschooling. In reality, the kids at public school sit at a desk most of the time. They don't get to socialize. Most activities are structured. Homeschoolers have CO-OPs, field trips, weekly PE visits, real interactions with adults, and actual free time. They are the most socialized kids in the US. The diversity in the homeschool relationships is quite large which you can see when a homeschooler has discussions with adults while their public school peers just quietly talk amongst themselves.
They are most tired of investing in R&D in the open and then having some company do a patent in their country. The company then sues them for infringement.
Two main mistakes that people make:
1. "scoop and dump" approach to flour. Flour should be spooned into the measuring cup so its not packed in.
2. over-baking cookies due to cooking too long or oven that is too hot or not hot enough.