Hacker News new | past | comments | ask | show | jobs | submit | makomk's comments login

In addition to the laws of physics and the engineering required to build TVs working against this, the EU deliberately changed the energy efficiency scale for things like TVs a few years back to specifically make an A hard to get and something that wouldn't be achieved by products currently on the market. They were probably too optimistic about future improvements too - a lot of TVs had to add special eco modes that aren't really designed to be used to meet the minimum efficiency now required by EU rules.

It's certainly not the only evidence of problems at NPR. For example, they managed to basically accuse Trump Jr of lying to Congress in a story that should not have survived basic fact checking: https://www.foxnews.com/politics/npr-issues-correction-after...

That Fox News piece actually understates how big of a screw-up this was. The key quote that supposedly showed Trump Jr claiming his dad's possible real estate deal in Russia had faded away by 2016, the one that was supposedly contradicted by Cohen's court testimony about ongoing negotiations, was in response to questioning about any possible deals other than the one Cohen was involved in - and in particular one specific potential deal with a different group of people. It's not just that it was brought up elsewhere in other answers that NPR missed. Merely looking at the immediate context of that key quote, the most basic thing we should expect of old-fashioned fact checking, should've been enough to flag the problem. The fact those other negotiations had in fact been brought up was literally the whole basis for that line of questioning.


The Chilterns, I think, and burying the line in tunnels was more or less necessary anyway. Some of the tunnels could technically probably have been replaced with cuttings, but apparently it would've cost more. The existing line used them mostly because tunneling was a lot harder back then. Mostly, the NIMBYs seem to have forced the existing tunnels to be longer than they need to be, which is expensive but not making building infrastructure in the country entirely non-viable levels of expensive.


Homebrew 6DoF tracking is definitely possible. I've had a janky and undocumented setup for a while that uses a standard smartphone as a display, paper and cardboard AprilTag markers with a computer and webcam for outside-in tracking, and homebuilt controllers. It requires a lot of improvement and is very sensitive to lighting conditions though.


I'm not sure it is. The EU has increasingly strict energy efficiency requirements for washing machines that are frankly stupid - they're pretty efficient already, so the way that manufacturers have improved efficiency through ludicrously long multi-hour wash cycles that keep on getting longer (there's apparently a direct relationship between the length of the wash cycle and how little energy can be used to clean clothes). The efficiency gains make washing less useful and consume more of people's limited time to the point that the cycles those numbers are based on don't really seem to be intended to be used.


That money has already gone out to people though. The reason that people's pay has bought less than before is that a large chunk of the economy was shut down and those goods and services were not produced. This means that there is simply no way for people to be able to purchase as much as they did before because it's just not there to buy in the first place. Shutting down the ports makes this worse by preventing US-based factories from getting the inputs to operate and non-US-based factories shipping their products to Americans. This is effectively making the whole country poorer in real terms as leverage to try and get a bigger share of what's left.


The basic reason this happens is that people's wages are only worth what they can buy, and in order for them to be able to buy those things they need to be produced and shipped. Sure, you could argue that this doesn't actually matter in practice because the corporations will always have enough excess profit to just pay people higher wages and employ more people to do less when the unions demand it, and that they'll have to do so rather than increasing prices, and that these cuts in profits will somehow always come out of the pockets of unsympathetic billionaires rather than ordinary workers' pension funds. That requires a lot more about the world to work out just right compared to the economics 101 version though.


As far as I can tell, this isn't actually true: "the DNA evidence that was not destroyed by the state is exculpatory". The Innocence Project are being very careful with their wording here. Initially, they relied on trace DNA on the knife that didn't match the accused murderer, but that ended up being from someone in the prosecutor's office handling it after it had been processed for forensic evidence. Then they tried to argue that this showed the state had destroyed evidence which would've proved his innocence, but the courts didn't buy it because all available evidence suggests the killer's DNA was simply never on the knife. (Which isn't that surprising - DNA evidence isn't perfect and gloves exist.) The other "forensic crime scene evidence" seems to be hothingburgers like a few non-matching hairs in a house that'd had a large number of people going in and out in the recent past.


DNA evidence is where it's hard to get a false negative then false positive.


All available evidence suggests there's nothing "classified" or "wartime ready" about these - they were your basic, cheap, totally unencrypted POCSAG/Flex pager. The same as any other pager carried by doctors and all the other people who use them - aside from the hidden explosives, of course.


In theory you should just be able to set -march to the lowest common denominator kind of CPU you expect your code to run on and it'll avoid relying on SSE if appropriate.


An x86_64 toolchain is allowed to assume SSE2 is present, it's mandated by the AMD64 spec.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: