Cops come to my door, I have nothing to say to them unless they have a warrant, and not even then.
No, you can't come in—in fact I'm coming outside and closing the door behind me. No, I'm not answering any questions (other than my name, as required by law).
10 I ask, "Am I under arrest?"
20 If they say, "No," then
30 I ask, "So I'm free to go back inside?"
40 If they say, "No," then
50 Goto 10
The speed issues were definitely a huge problem. Every Ruby on Rails project I've ever run on my test server, including the super-simple to-do list given in the tutorials, have ground the execution of said project to a halt; something that would take PHP milliseconds to do would take 30 seconds minimum while Ruby fired itself up.
Personal Anecdote FTW!
Unlike you, I wrote, deployed and maintained a RoR app in a professional environment that got a minimum of 40,000 hits per day, every day. It worked like a champ with no speed issues, because a) I worked with the server guys to ensure the web, application and database servers were tuned, and b) I know how to use a profiler.
I wouldn't dream of using PHP because besides being one of the few languages where every feature is broken in some way, I needed TDD and MVC baked in as well as threading support.
I would've used Java, but (as usual) the artificial deadlines required rapid deployment, and the minimum viable product would've taken too long to code in Java. I could've just as easily gone with Perl, but using some gems that allowed me to basically drop them in and go saved lots of time I would've wasted coding the same things in Perl (even though CPAN rocks).
Before bowing your head, please turn to page 5 in your hymnal:
Partition ye diske unto me.
Anon.
Because Mountain Lion isn't THAT much of an upgrade over Lion, and whatever comes after (HouseCat?) will probably be more IOS-like—i.e., sucky on a laptop.
Until/unless Apple de-fscks itself, the upgrade path will be via Linux on Mac.
U.S. District Judge Lewis Kaplan's opinion said that the eavesdropping technique "functioned whether the phone was powered on or off." Some handsets can't be fully powered down without removing the battery; for instance, some Nokia models will wake up when turned off if an alarm is set.
[snip]
The U.S. Commerce Department's security office warns that "a cellular telephone can be turned into a microphone and transmitter for the purpose of listening to conversations in the vicinity of the phone." An article in the Financial Times last year said mobile providers can "remotely install a piece of software on to any handset, without the owner's knowledge, which will activate the microphone even when its owner is not making a call."
Remember, that was 6 years ago. Those civil rights you thought you had? Hope you enjoyed them at the time.
...until you are.
And by "interesting enough," I mean
etc.
See what I did there?
If there was some kind of penalty or cost (say, a paltry fee of $1 for every take down notice filed), we'd see these things dry up faster than a river in corn country.
The penalty for them is much less than the street justice penalty they want to hand out.
You do have real evidence for this, right?
This isn't one of those "Fox 'News' says Islamists want to kill me in my sleep so I better vote for Romney or everyone I know will get their heads cut off" knee-jerk fear of the other taken to the logical absurd end, right?
I was tweaking the AC's reliance on Argumentum ad Verecundiam, which is (often) a fallacy.
I looked up alternatives to Alzheimer's, and Pick's Disease looks like an introvert-troll/basement-dweller's dream. Check out the list of behavioural and emotional changes.
Speaking as a professional SQL Developer with OVER TWENTY YEARS of experience, an RDBMS is not the answer to every problem. Sometimes NoSQL makes sense.
For example, if I'm dumping some random user data that will never be formatted/standardized/normalized—that can be different domains for every user—NoSQL might be the right choice.
Maybe I want to store a user's favorite object (puppy, car, toy, steak 'doneness') and I don't want to have a child-table-from-hell lookup table. NoSQL is a great option.
On the other hand, if I want to do some sort of row lookback, then it is far easier in a relational DB. For example, if I want to find the salary average and of all of people in the same department as the most recent new hire or the average working 'lifespan' (how long before the person quits, gets fired or dies) of every department vs. their salary range*, then it is pretty easy.
Now get off my lawn.
* Yes, real-world examples.
... because the logical conclusion is without continuous recording, the airport—and eventually the entire country—will be overrun with child pornographers.
I mean, look at what happened over the last 145 years: thousands, if not millions, of child pornographers have been rattling at the gates of poor Canada, trying to get in. Why do you hate Canada?
No, I say let them film, x-ray, record, and take DNA samples of every traveller. Because if they don't, then someone's child, perhaps my own, will get pornographized. It is an unescapable fact.
We have a equal opportunity Calculus class -- it's fully integrated.
