sorry - s.trokes.org was just a clone of bl.ocks.org with syntax highlight support for clojure. I've updated the links to blocks and the examples are working again.
I don't think you read the article - the metals were the direct result of fertilizer which would not be allowed in organic farming. The catch is that the fertilizer (coal ash) was used to grow corn and soybean animal feed (which cows can't even digest properly, but that's another story...) and then the manure of those cows went to organic farms - so the purported vector of attack was indirect.
I'm no cheerleader of organics and think it's foolish that GMOs are by definition non-organic. However, I buy them when I can primarily because of my concerns with pesticide and fertilizer overuse.
I'm not sure that's how I understood the article. Did you see the part that said "This proved kale’s powers as a hyperaccumulator, but it disproved, or at least shook, his belief that coal ash was the culprit."
The catch is that the fertilizer (coal ash) was used to grow corn and soybean animal feed (which cows can't even digest properly, but that's another story...) and then the manure of those cows went to organic farms - so the purported vector of attack was indirect.
That's exactly my point though, organic farming is not a closed system no matter how much the public might desire to believe it is. There are some tenants of growing organics but it's not standardized nor systematic. I believe it is potentially deceiving in the worse cases. Of course the issue at hand is not organic farming but instead cruciferous veggies such as kale and broccoli but I only mention the idea because it's an integral part of Hubbard's "perfect storm":
"Now, Hubbard had what he often calls “a perfect storm”: contaminated vegetables, misleadingly pushed on the public as nutritious—and clean—leading to misdiagnosed ailments. “Where does this list end?” he wrote in one of his numerous messages emphasizing these points. “There is undoubtedly a series of similar perfect storms at work in other heavy metals and our food supply, including infant/baby foods, pet foods, and beyond.”"
But if everyone grew "organic" food, then it would be moot point. A full organic system is a better than a full non-organic system. So while current organic food might be contaminated through side channels, making more of our food production 'organic' would be be beneficial - not because organic food is great nutritionally in and of itself, but because having more of it benefits the food system.
That said, I don't eat much organic food. However, this article has made me want to eat more organic food.
It's because on a terminal, CR moved the cursor to the left column and LF moved the cursor down one line. That was also true for dot matrix printers, and paper-based terminals like a modded IBM Selectric or the DecWriter.
So if you wanted your file to display properly when type'd to the console or pip'd to a printer, you needed CR,LF make it work. LF alone would give you text in a barber pole pattern, and CR alone would give you the last line of a file on a terminal, or a horrible mess of over strike text on a printer.
Ah, I remember those days. If someone made the mistake of just using CR alone in a big file they spooled to the lineprinter, it sometimes quite literally would halt and catch fire. There was a fire-extinguisher placed next to it for a reason.
GDP is like measuring calories burned without any other context. Expenditure is a means, not an end.
As engineers I think we are aware of the danger of optimizing around the wrong fitness function. The GDP is used as shorthand for "the economy" in federal policymaking, so now there are many ways to "stimulate" the economy by creating various forms of inefficiencies and misery. [1]
Certainly you've heard a government official frame an issue he didn't like as "bad for the economy"? In the US, it's basically the first page in the playbook for both sides of the aisle because very few issues are as sacred as a healthy economy. But if hurting the economy just means bringing down the GDP, then there are countless reasons why the underlying issue might still be beneficial to the welfare of its citizens.
Want to boost your country's GDP? Here's some tips. Become terminally ill. Get involved in a costly divorce. Try gambling or drinking habitually. Take a job where you commute long hours wasting gas in traffic. Hell, open a strip mine - every resource extracted is a net positive on the national ledger. Bonus points if you can coerce your fellow citizens into compulsory spending - a nasty coal plant triggering asthma in the local population is a great example.
Even worse, a focus on GDP directly contributes to income inequality because as a measure it is blind to the distribution. If the top 1% gain more than every one else loses in a year, GDP still rises. For this reason Rowe calls GDP a "statistical laundry operation that hides the suffering at the bottom".
Measuring and tracking GDP is a splendid idea, but using it as even a proxy for national welfare is insanity. I encourage anyone interested to read the linked article, which is as true today as when Rowe testified before the US senate 8 years ago. Also at the end he takes a first pass at laying out principles around new metrics to fix the situation.
It's not merely used in policy making: GDP as a metric basically emerged for policy making in the contexts of resource allocation during the Great Depression and war planning during WWII. (And arguably during prior wars before that: http://www.google.com/search?q=invention+of+gdp .)
Article fails to mention: the eyes of the squid and octopus are very similar to ours in overall structure, but are not "wired backwards". So it seems that any explanation of why backwards is actually "vision-enhancing" is incomplete unless it also explains why it would not be enhancing for the squid. (though perhaps a justification could exist based on different wavelengths and lighting conditions underwater)
Some context for this code can be found here [1] in Lammers' great book.
Gates specifically says that "not a line of code went out that I didn't look over" for the BASIC 6502 product. At the time (1986) he said he considered BASIC for the 8080 his "greatest achievement ever in programming" and admitted that he no longer programs himself but does was still looking at code and discussing algorithms with his 160 Microsoft engineers.
It's my understanding that - because of obscure constants in the git codebase - it's a bad idea to use dates before Sat, 03 Mar 1973 09:46:40 GMT because the usable git epoch is 1970 + 100000000s. More details available here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625480
FWIW: I routinely start my git repos with an empty commit to allow history rewrites and use Jan 1st, 1974 as my own epoch.
Note that in the US, protections are broad and being funny doesn't matter. Legal precedent clearly states that "First Amendment protections do not apply only to those who speak clearly, whose jokes are funny, and whose parodies succeed" [1]
We have 2 Live Crew to thank for firmly establishing this majority opinion in US Supreme Court 20 years ago.
