brucedawson

Unfortunate typo: the article says "Having placed the fresnel lens, we're not able to get an usable image on the whole 40x30cm sensor." but I think the "not" should be "now". Having "not" reverse the meaning of the critical sentence!

It's easy to make these 800V systems totally safe. You just have to combine this idea with the extremely sensible plan to put data centers in space and then there will be no worry about when "someone pulls out a rackmount unit" because there not be someone within hundreds of kilometers.

I think that is correct, but yes, a delay-slot instruction that is always executed is easy to reason about. Speculative execution that gets real? shudder

It did not help that the performance of the Xbox 360 CPU (and Cell) was terrible. In-order execution without the crazy-high frequencies the CPU was designed for was a failure.

Author here: This is not a common problem. I think I was told that Alpha had basically the same bug but it is a bug, for sure. Speculative execution causing problematic side effects is a deal killer.

Speculative execution, however, can cause less problematic side effects. For instance, a speculatively executed load or prefetch will usually actually prefetch which will pollute the cache, TLB, etc., and reveal side-band information, but that is a performance problem and perhaps a subtle security flaw, not a correctness bug like this was.

In 2021 I found an invisible memory leak in a tool (VS Code) that I have never used. This is the story of how.

I was surprised also when this happened, but pleased. The trust was nice. The fact that they needed to give me the symbols in order to understand the issue was surprising. Why couldn't they find the calls in their source? Or analyze the trace themselves? Curious.

Whoops! Good catch. That was supposed to be 12 furlongs. Apparently I have no intuitive sense of how long a furlong is so I didn't notice my typo

That is a problem they haven't tried to solve. Driving directions could be for tax/ride-share or a person in their own car. If Google Maps doesn't even ask you which it is then it can't possibly reliably give you correct directions. I'd love to see that fixed.

Right. I (the friend's cousin) did that. And two weeks after the changes were supposed to take effect the directions are still broken and the customers of this business are still inconvenienced.

So I wrote a blog post. It is yet to be determined if that will help or not.

Given that Google Maps understands the rules for street addresses in Vancouver it seems like the problem shouldn't have happened in the first place and should have been auto-corrected and the fix should have been quickly accepted. But none of that happened.

Most non-nerds don't know how to use the feedback tool. That is the reality.

It drives me crazy that Google Maps sometimes asks me where the entrance to a building is but it never seems to be clear about what it is asking. Where a pedestrian would enter? Where a car would enter?

Driving directions are a wonderful thing but they need to account for whether you are arriving in a ride-share vehicle (please drop me at the front entrance) or in a car you need to park (the front entrance may be worthless) - lots of work yet to be done.