rza

there's only one reason you lock up merchandise

This might have been a good article had it not been for the pretentious, holier-than-thou introduction. Apparently enjoying the fruits of a modern life make you a mindless drone compared to the "contemporary fine artist" who lives on a boat or someone living in a forest re-inventing the wheel for every modern necessity.

Actually, wouldn't it be that the black King would just capture the Queen?

The question was actually about the portrayal of US motives during WW2.

Should we start banning repos with "master" and "slave" too?

I don't know much about network security. Is there a difference between the kind of attacks that would be caught by honeypots vs targeted attacks? Do these statistics depend heavily on how they setup their honeypots, which I assume is limited by the company's logistics.

This graphic really just plays into the hands of climate change deniers. No labelled axis, a timeline of only 100 years (you could also argue the dinosaurs caused global warming), and the quite proud declaration at the end the argument is really "no contest" under the assumption that correlation == causation. I could also make a graph that shows the increase in global temperature correlating with the rise in the Latino population, could I then declare it a "no contest"?

Anyone know what happens when you allow bloomberg.com to use your camera when you finish reading the article?

I also believe hackTime() was added to the DateTime() API in Java 12, which wasn't released until 2011.

Great concept, my main grip with meeting people on say a site like Meetup is that every event has like 100 attendees and smaller ones are too niche when all I really want is to have a conversation with a few people.

The default setting is that when you view someone's profile, it tells them who you are. I turned this off, as I would love to be able to browse without notifying every profile I go to.

> "...immediately realize that which will make it more difficult to modify these functions". Please clarify what you mean here.

I absolutely would prefer a method to look like:

def main():

  SetUp()

  try:

    DoStuff()

  except:

    HandleErrors()

then a thousand-line god function. It encourages modularity, reduced state and scope (please ignore my example above which implies a lot of shared state:)), and every method should be well-named and do a single thing well. Maybe for super-sensitive realtime systems, this might cause a few necessary checks that we could ignore, but we are talking about readability here.

Having to navigate between different methods is honestly a really lame excuse for sticking everything in one method. That's what IDE's, documentation, and good method names are for.