Comments URL: https://news.ycombinator.com/item?id=46360478

Points: 3

# Comments: 0

I wonder how you figure out when your codebase has reached 95% safety? Or is it OK to stop looking for memory unsafety when you hit, say, 92% safe?

It wasn't an easter egg; it was how the games accessed and played the in-game music (and digitized speech when that was a new, exciting thing). There would be one huge data track and then dozens of small audio tracks. If the game did take multiple CDs, then either (a) you installed all the discs but all the audio was on the CD that had to be in the drive for the game to play or (b) each CD had the audio needed for the levels that were on that disc (I think that scenario was more common on PS1 games, but I could be mis-remembering)

In theory that sponsorship money could stay local, if the people who saved money by buying cars direct from Ford gave it personally to the local sports teams instead of giving it to Bob first.

No, it's like finding out your neighbor sold a bunch of faulty locks to a bunch of other people. There's a difference between information that would benefit only one person (the neighbor in your analogy) and information that would benefit many people (the neighbor's customers in my analogy)

More than the internal injuries that could be caused by water forcibly entering the vagina? Probably not.

This must vary by state; I recently took out a small loan from my local bank in Pennsylvania and the information I went home with came out to about 15 pages.

>When you're dealing with huge amounts of yellow tape and you have millions of customers

I thought the conventional wisdom was that onerous regulation actually favored huge businesses with "millions of customers" -- for example, the effort of having to "print that, audit it, have lawyers look it over, maintain it" is a fixed cost so the cost per customer is smaller for larger banks.