273 karma · joined October 27, 2018
There is always a message and the line between fiction and nonfiction isn't always clear. Who is making the media and why, who did the research, who funded the project, etc.
What's sad and scary is that media literacy and critical thinking isn't a top priority for teaching in schools.
'The islands with too much power' https://www.youtube.com/watch?v=8UmsfXWzvEA
func canThrowErrors() throws -> String
func cannotThrowErrors() -> Stringhttps://www.theguardian.com/world/2019/jul/05/how-britain-ca...
Firefox is great yes, viva la resistance. Unfortunately I'm seeing more sites with quirks on Firefox so I tend to use both Firefox and Edge.
1. How is this 14.5% number calculated? Does it include deforestation? Grass-fed is far different than deforesting for grazing land or crop land.
For instance from the FAO PDF you quoted: "extensive livestock are often kept in remote environments where deforestation and land degradation reflect weaknesses in institutions and policies". The headline then should read "deforestation and bad land policy causes climate change" not "stop eating cows".
2. Again, how are these 10x numbers calculated? Comparing e.g. industrialized agriculture to inefficient agriculture in a third-world country is not going to convince skeptics. If beef production is extremely inefficient somewhere, we should fix that.
3. If country A emits 100x the CO2 production of country B for the same end result, that needs to be noted. If my neighbor has a giant gas-guzzling monster truck spewing emissions, my neighborhood is not at fault, it's just him.
4. Agree 100%. We should be addressing the deforestation. Saying "stop eating meat" is not the solution. "Don't buy food from Brazil grown on land that had rain forest last year" is more nuanced and probably easier to follow. Matter of fact, don't buy products made by totalitarian regimes, slaves, child labor, etc. We should know where and how our products are made. I'm not advocating "don't buy sneakers" because some sneakers are made in unethical ways.
5. Humans love meat, that fact is not changing anytime soon. We should advocate for more efficient (and yet more ethical). If we need to, governments should pass laws to make production sustainable similar to what is done to prevent overfishing.
6. We have a perfect machine, well studied and used for millennia, for converting corn husks and other inedible things that would otherwise be thrown away into fertilizer: cows. Bonus, in addition to fertilizer, you get milk, hides, bones, highly nutritious meat, etc.
7/8. Totally agree. More laws need to be passed to regulate this industry, it's truly sickening. All meat products should be twice as expensive or more as they currently are to account for this.
https://www.jtolio.com/2016/03/go-channels-are-bad-and-you-s...
Last I saw, this was still being debated by the LDT and weighed against similar proposals such as introducing a `defer` keyword like Swift/Go.
I highly recommend watching for more details. https://www.youtube.com/watch?v=SdrhpThqlCo
I wonder how many of the same arguments were made about Java back in the day. Java got generics at around 8 years after its 1.0 release in 1996. Go's getting them 9 years after its 1.0 release in 2012.
We should probably compare apples-to-apples. C++ has been around for 35+ years. Java has been around for 25 years since its 1.0 in 1996. Python for 26 years. C# for 20 years.
I wonder what people will think of Go in 10-20 years when its age matches more established ecosystems. Will devs be complaining about dealing with pre-generics code then?
I'm arguing against the logic: "every big company always ends up being a den of advertising evil". Cherry picking examples like Google is not proof of this.
Not every company is Google or Facebook. Is Apple selling its soul to advertisers tomorrow? Is Netflix going to insert ad breaks every 5 minutes any day now? Is Tesla going to have you watch an ad every time you start the car?
The fact is, a number of companies control a huge number of eyeballs. An unethical exec taking advantage of that would cause enormous PR nightmare. If you're making money with a great brand reputation, you don't mess with the recipe.
But totally agreed it needs to be common knowledge that everything digital can potentially be bogus. This stuff should be taught in schools from an early age honestly.
[1, 2, 3] & map (* 3) & filter (> 4) & sum
This takes the array, maps it, filters and sums it in one go. If the array was say 1,000,000 elements and you used multiple `map`, `filter`, and other similar functions you'd soon run out memory (or use much more than needed) if they were eager and allocated a million-element array at each step as opposed to running through the array one time.The alternative is to use imperative style (for loops and such), but the functional style is often more declarative and easier to read and write (think SQL).
> vanishingly few U.S. policymakers have degrees in science or foreign languages, and yet they nevertheless make decisions regarding nuclear weapons, biotechnology, and international trade.
Has any society ever had educated politicians as the norm? It seems like politicking is a skill in itself that leaves no time for other education (with few exceptions such as Jimmy Carter).
> the competitive testing regime systematically favored the wealthy and the connected—who thus had more reason to continue to support it.
Nothing new here, but
> A need for government revenue led to the development of the “irregular” route for advancement, in which offices and degrees could be purchased rather than earned. Between 1830 and 1912, only 32 percent of Qing officials had actually passed the examinations
That's a bit shortsighted of a policy no? Codifying the outright buying of political office is a bit different and more extreme than buying influence we see today (and throughout history). Maybe a real historian could speak to this bizarre policy.
select * from A a join B b on b.Id = A.OtherId
SQL IDEs will auto-suggest that "on b.Id = A.OtherId" because it's the foreign key and could be inferred. That's what you need 99% of the time.But this article is thought provoking to say the least. It follows the courtroom logic of holding the defendant SQL on trial for as much as possible. And SQL is guilty of a lot of crimes.
I do hope GraphQL and similar query languages become more prevalent and standardized, as it seems SQL could really use some stiffer competition.
Here's `is-number` (https://github.com/jonschlinkert/is-number/blob/master/index...):
module.exports = function(num) {
if (typeof num === 'number') {
return num - num === 0;
}
if (typeof num === 'string' && num.trim() !== '') {
return Number.isFinite ? Number.isFinite(+num) : isFinite(+num);
}
return false;
};
Care to explain why these 5 lines of code need to be a package? To me, having something so simple be a package by itself is absurd.