> Take Herb Sutter for example, who argues that "memory safety" as defined in this article is an extreme goal and we should instead focus on a more achievable 95% safety
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?
A coin deposit is no more a mark of a bad neighborhood than having cart corrals in the parking lot -- like them, it is a way of reducing (or trying to eliminate) the amount of time employees have to spend collecting carts and returning them.
>so putting the OST in CD format was a nice easter egg.
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)
>I like money staying local, seeing kids sports teams sponsored by Bob's Ford
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.
>It's like finding out my neighbor doesn't lock his front door at night and announcing it on twitter.
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)
> When they are cast to the shadows they can grow,
It's a nice poetic conceit to think of good ideas as thriving in the light like flowers while bad ideas flourish in the darkness like mushrooms, but they both thrive on the same thing -- attention. To make another comparison with things that grow in the shadows: the crawlspace under my front porch is full of bugs and critters, but they didn't get there because I cast them out of my house, and I don't keep my house bug-free by periodically inviting them in for debates.
FTA: It is available first today in the July release of the Python Extension for Visual Studio Code, and we will later release it as a standalone component that you can use with any tool that works with the Language Server Protocol.
>Every time they write a loan they are forced to provide the customer with a 200-page "book" of all the compliance and regulation surrounding that loan.
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.
>That some genetic features may be dropped or changed if not required anymore without the pressure of a higher death rate / lower reproduction ... darwinism doesn't seem to explain everything
If the results of a newly-introduced selection pressure can be explained by darwinism / natural selection, then surely so can the results of a removal of selection pressure.
For example, if there are genes that result in lowered fear or agression, and that leads to fewer offspring for wild mice, they will have a lower frequency in a wild mouse population than in a population where they don't lead to fewer offspring. I'm no expert, but it doesn't seem like this particular article requires any additional mechanisms beyond natural selection.
>...One of talents greatest contributions is knowing how to let your winners run and cut your losses...
>...talent would understand what events are more likely to succeed...
If we already know that these things are the result of talent and not luck, and if it's a foregone conclusion that the model gives an "oversized role" to luck, then I guess these kinds of investigation are doomed from the start.
>where metaphors have been mistaken for new words.
Dictionaries have included metaphorical definitions for ... at least 60 years? I have a 1958 Webster's that defines "feather in one's cap" and "hard row to hoe" and probably quite a few more.
Given the rate of startup failure, and the sheer number of other companies whose "product wasn't there", what reason do we have to believe that hiring a diverse workforce is more relevant than all the other possible reasons for not creating the best possible product?
The formula for constant growth over time, for example, a 2% increase every year, would be starting salary * 1.02 ^ t where t is the number of years. So there is an exponent present, and constant growth is an exponential process.
I think for circularity you'd need a pair of definitions -- "programming: making a program" and "program: the result of programming". In this case, we already know what a program (or a "programmed solution") is -- that is, we can tell that something is a program without necessarily knowing how it was made. So the definition at least provides some new information on top of that -- the name for the activity of creating programs.[1] Also, by including the concept of "design", it lets you know when the author says "programming", he doesn't just mean the acts of writing source code, or typing it in.
[1] You could have probably guessed that the name was going to be "programming", but it might not have been.
>It might even explain why so many cultures had rites to male adulthood involving extreme pain.
Unless you believe that the rites were created to address the problem of "one day, there will be analgesics with antiandrogen effects, so we'll have a few centuries of practice at enduring extreme pain", then I don't see how there could be any connection.
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?