Ah nevermind, I got it. It's not terribly obvious though...

Look, I'm not picky or anything, and I know headlines are shortened, but what the hell does " Apple Said To Team With Visa, MasterCard On iPhone Wallet" mean?

Software monetization is basically just like anal sex. You keep on pushing until the person you're doing it to can't take it anymore. And then you keep pushing.

You seem to know a lot about monetizing anal sex...

That's how I feel too: they've turned Firefox into a cheap whore - albeit with an opt-out option.

Yet I realize they have to make money to keep bringing out new Firefox releases.

Yet... it sucks. Ads sucks. Ad-funded internet sucks.

Agreed. My collection includes a Guantlett 2, Tempest, Ms PacMan, Xevious, Robotron 2048, and Smash TV (not in original cabinet). The rest of the modern stiff pretty much pales in comparison.

Anybody that would consider her being a hate-monger is out of touch with reality.

When a police officer is around you, you are being surveilled - by the police officer. If you're doing anything illegal in front of the police, expect to get in trouble. Police wear uniforms and are easy to spot. That's very different from having concealed cameras everywhere.

Sorry, old Unix guy here. My first reaction was "What the F is pkexec and why is it running setuid?"

Yet another way to execute arbitrary privileged executables is yet another potential security hole. This dumb thing is apparently part of the "Free Desktop" but it's depended on by all kinds of stuff including the fricking RedHat power management. What's wrong with plain old sudo?

1) if you make exploitation less likely than an astroid hitting the earth, then for all practical purposes you can say that it is prevented.
2) 'repeatable crash bug behavior' doesn't matter, it will be repeatable if it is run in valgrind/address sanitizer or via a debugger which is really all that matters to a developer. An end user couldn't care less about repeatable crashes and would prefer if it occasionally/usually continued running.

No, that's not right. You have to pull the finger. I'll show you. Pull my finger.

I don't know what's worse: being blown out of the sky with explosives or having to stay in Phoenix.

The question is, who is "you" and when does that checking happen? I don't do a lot of work in Python, Ruby, etc. and all of the programmers that I know who do are fairly young and working on fairly small projects so they don't have a good answer for refactoring.

If I change the arguments to a method in a statically type language any place where I forgot to change the call to that method will be exposed at compile time. As far as I've been able to learn so far, in most dynamically typed languages that check won't happen until runtime. The pat answer to that is "you should have unit tests that cover everything" - but getting complete code coverage is hard and for large projects, the test suite takes a non-trivial amount of time to run - usually much, much longer than compile time. So, you wind up with bugs at runtime. Or is there a better solution?

OK, that's bullshit.

I'm reminded of the old joke:
"What famous event happened in 1732?"
"George Washington was born."
"Very good. Now what famous event happened in 1743?'
"George Washington became 11 years old."

It must be an old joke alright, cuz I've never heard it, and it ain't funny.

Correct me if I'm wrong but... would you happen to be rooting for India by any chance?