HN user

jcl

5,205 karma
Posts13
Comments1,963
View on HN

The impression I get from the article is not that the compiled code of each implementation produces the same object code, but that when the implementations are run with the same inputs, they produce exactly the same output — that is, the same JS VM bytecode.

I hiked up there once… There was a reservoir with a trail around it and, to my surprise, a fenced-off area full of goats. Apparently they were part of a vegetation control program used in the parks there.

I wasn’t sure what the article meant by “no screws or glue”, when the photograph appears to have visible screws. But closer images show that these are apparently some sort of rivet?

I found a (Japanese-language-only) news piece that shows some of the crafting and assembly of the satellite, and the box body certainly holds together by itself, via some beautifully intricate joinery:

https://www.youtube.com/watch?v=A_F-NzzC7RA

My understanding of the article is that some companies added sesame to their products and ingredients label, while others may have changed their label to say the product “may contain” sesame — but that Bimbo did neither of these things, instead changing their label to say that the product definitely contained sesame, when in fact sesame was not an ingredient.

As Monty Hall pointed out in interviews, he was not obligated to offer the opportunity to switch and sometimes did not. So in this case knowledge of the actual show may have contributed to confusion.

https://en.wikipedia.org/wiki/Monty_Hall#Monty_Hall_Problem

(But vos Savant stated in later columns that most of the critical responses she received assumed that the host was obligated to offer the switch, so they were genuinely confused by the paradox.)

There are actually 10,100 equally likely situations: 101 choices of N x 100 choices of ball. When you completely discount the N=0 case, it’s because all choices of ball are green. You similarly need to almost completely discount the N=1 case, because almost all choices of ball in that situation are green, etc.

Yes, it’s a mistake to take the expected value before the ball is drawn, because the drawn ball adds information, disproportionately changing the expected value.

Consider an alternate game, where I flip a hidden coin… if it is heads, I let you pick from an urn with 99 red and 1 green; if it is tails, I let you pick from an urn with 1 red and 99 green. The expected number of red is still 50, and the chance of drawing that first red is still 50%. But once that red is drawn, your expectation of what the next draw will be should change significantly.

I thought Southwest uses “open” seating, where passengers aren’t assigned a seat, but instead just take any unoccupied seat? If so, a perk of being earlier in the boarding order would be that you have a better chance of getting a seat you want, if you have any particular preferences.

So, it seems that the intent of the code is to add two parallel, invisible kill beams to augment the main beam. The nature of the bugs are such that the added beams are positioned in roughly the right place, for a certain axis-aligned view.

I’d guess that the feature was tested manually in such a view, and seemed to work OK. And that the feature was subtle enough of a behavior tweak that no one noticed that it didn’t work correctly in most other situations, since the main, visible beam worked correctly, and no one could see it killing enemies behind walls.

True, but both of those examples were written for the general public, where the authors might intentionally be using “symptom” in its colloquial sense to be better understood. So it’s hard to draw conclusions about how the same authors would use “symptom” when writing for a medical audience.