Hacker Newsnew | past | comments | ask | show | jobs | submit | msl's commentslogin

That story is easy to understand and thus catchy, but it is not true. The cause of those 1201 and 1202 alarms is a lot more complex, but well worth taking the time to understand if you are into the topic. Wikipedia offers a short description [1] to get you started.

[1] https://en.wikipedia.org/wiki/Apollo_Guidance_Computer#1201_...


GP did not suggest anything of the kind, though. They talked about "figuring out where to look" which very different. In that kind of use, it doesn't really matter that the model might hallucinate or draw faulty conclusions, as you're not using it figure out what to do, how or why. The only thing it is telling you is where some information is located, after which you go check it out from the actual source of truth. If the reference turns out to be wrong, you'll notice immediately.


Imagine being so well off that you don't even notice being off by ten orders of magnitude. Meanwhile, there are people dealing with negative exponents.


You don't get to call it "stepping out of line" if there are no consequences for doing so. See for example how the My Lai Massacre was handled[1]. The pattern continues when it comes to shooting down an airliner[2], an airstrike on a hospital[3] and many more cases.

If no-one ever gets more than a stern talking to, then clearly there is no line. These actions are as close to adhering to policy as you can get without saying it outright.

[1] https://en.wikipedia.org/wiki/My_Lai_massacre#Investigation_...

[2] https://en.wikipedia.org/wiki/Iran_Air_Flight_655 (there is even less to see about the aftermath here: everyone got a medal)

[3] https://en.wikipedia.org/wiki/Kunduz_hospital_airstrike (this time someone was disciplined)


#1 looks like a case of poor incentives which were a little too flexible as a result of what they were up against from the guerilla fighters. every army has elements that can get out of control if not kept on a tight leash, the US is no different in that regard. the difference is that we will identify and correct it if we see it.

#2 looks like a legitimate accident. technology wasn't as good as it is now. there were apologies and payments to the Iranian families. it sounds like they tried to follow protocol.

you can look at other countries who have shot down commercial airliners to see that this wasn't unique to the US in any way. the difference is that we tried to communicate and verify first, when many other countries didn't.

#3 just looks like a largely human mistake, which was recognized by multiple people involved privately and publicly. it's possible if they picked coordinates and had a database of protected locations, it could've been flagged, but i don't know if something like that exists. the nature of some of these decisions is that they have to happen fast, but that means your process has to be really good to avoid mistakes.

you also didn't mention the case where we drone striked a vehicle with kids in it and we publicly apologized for it. these things do happen, but considering the extremely large number of strikes the US tends to do, these are relatively rare.

because our society does value truth when it matters, it usually makes it out if there is substance to it. in many other societies, the governments can just perpetually deny and anyone who disagrees will be jailed or killed. that doesn't mean we don't have secrets like anyone else.


That description does not match the RCA 1802 [1] perfectly, but it is probably the best known microprocessor (not a microcontroller, though) without a dedicated program counter. There are a lot of misconceptions about it floating on the internet, so I would not be surprised to hear it described as you did.

[1] https://en.wikipedia.org/wiki/RCA_1802


Forcing everyone to use ourFetch is rubbish, but forcing everyone to use axios is clean and elegant? You might want to elaborate just a little more.


ourFetch is more likely to be buggy, unmaintained, undocumented and nobody knows it well because the guy who wrote it left the org 2 years ago and so you have to waste time reading and maintaining it yourself.

Axios is something where you get most of that work done for you by the community for free, and a lot of people know it. As long as you don’t get pwned due to it. Oh and you will actually find community packages that integrate with it, vs ourFetch, which again, nobody knows or even cares that it exists.

Applies to web frameworks, databases and other types of software and dependencies - if you work with brilliant people, you might succeed rolling your own, but for most people taking something battle tested, something off the shelf is a pretty sane way to go about it.

In this case it’s a relatively small dependency so it’s not the end of the world, but it’s the exact same principle.


> In this case it’s a relatively small dependency so it’s not the end of the world, but it’s the exact same principle.

An alternative world-view is: "A little copying is better than a little dependency," from https://go-proverbs.github.io

Does become subjective about what "small" and "little" are though.


I also agree with this!

I think the ideal model would be being able to depend on upstream code, but being able to review ALL of the actual code changes when pulling in new dependency versions (with a nice UI) and being able to vendor things and branch off with a single command whenever you need it, so you don't have to maintain it yourself by default but it's trivial when you want to.

It's actually surprising that in regards to front end development the whole shadcn approach hasn't gotten more popular. Or anywhere else for that matter, focusing on making code way more easy to maintain, to compile/deploy, with less complexity along the way.


Exactly, I completely agree.

It's the difference between using a SQL library and some person on your team writing their own SQL library and everyone having to use it. There's a vast gulf between the two, professionally speaking.

People dissing axios probably suffer from other NIH problems too.


> Honestly, if coerced sideloading is a real attack vector, [...]

I don't believe that it is. I follow this "scene" pretty closely, and that means I read about successful scams all the time. They happen in huge numbers. Yet I have never encountered a reliable report of one that utilized a "sideloaded"[1] malicious app. Not once. Phishing email messages and web sites, sure. This change will not help counter those, though.

I don't even see what you could accomplish with a malicious app that you couldn't otherwise. I would certainly be interested to hear of any real world cases demonstrating the danger.

[1] When I was a kid, this was called "installing."


This is the thing that bothers me the most about this. It is as if even the HN crowd is taking it as given that malware is this big problem for banking on Android but in reality there seems to be very little evidence to back this up. I regularly read local (Finnish) news stories about scams and they always seem to be about purely social engineering via whatsapp or the scammer calling their number and convincing the victim they are a banking official or police etc.

That's why I'm inclined to believe Google is just using safety as an excuse to further leverage their monopoly.


UTF-32 allows for constant time access to code points. Neither UTF-8 nor UTF-16 can do the same (there are 2 to the power of 20 valid code points, though not all are in use).

While most characters might be encodable as a single code point, Python does not normalize strings, so there is no guarantee that even relatively normal characters are actually stored as single code points.

Try this in Python:

  s = "a\u0308"
  print(s)
  print(s[0])
You will see:

  ä
  a


No, the worst outcome is much worse than that. You need to keep track of what is going on around, or you won't be able to account for you surroundings when you start moving again. I see these failures all the time: a driver of a stopped car is distracted, then realizes that the lights have turned green (or, even more commonly in these types of situations, a space has opened for them to merge into or pass through) and they "have" to get moving, now. Now they are in a hurry, and obviously can't afford to take a moment to take a careful stock of everything going on around them, so inevitably, they end up missing something. Usually someone else (such as myself, pushing a stroller) will be able to react in time and an accident is avoided, but it should not go like that. If you can't or aren't willing to attend to traffic, get out of it.


In Finnish you might use "kuunteluttaa". You start with "kuunnella", "to listen" and inflect it in the way that turn a verb into "make someone verb". This particular example is a little unusual, but the same thing is commonly used with e.g. "taste". It works with all kinds of verbs, so it comes handy when you want your car serviced or your house painted.


Thanks for showing :)


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

Search: