You are trying to argue semantics and failing dismally. A corporation is not a living entity and therefore robbery of the corporation is a civil crime. Does that explain it in simple enough terms for you now?

This really isn't that difficult of a concept, and your arrogance is misplaced. Corporations are OWNED by citizens, either privately or by shareholders in a public company. They are the victims of this crime. Value was robbed from the corporation, and thus from the owners of the corporation. No one is arguing that a corporation is a living entity. You're somehow trying to argue that if someone breaks into a warehouse owned by a corporation and steals widgets, it's only a civil action since corporations aren't living entities. That's just silly. Theft is theft, and someone owns what was stolen.

There's more to accuracy when you're dealing with fat fingers than the hardware.

I think the issue is generally more of a software problem than an IPS problem.

I don't know what IPad you're using, but that's one of the things that impresses me about it.

Coincidentally, I was just playing with one at Best Buy today, and I have to say that it doesn't suck nearly as much as other iPad competitors. But that's somewhat damning it with faint praise. The interface is still much more sluggish and choppy than an iPad. The screen still doesn't feel nearly as precise. Given that the price is the same as the iPad, there really isn't any reason not to get an iPad, unless you really just hate Apple. Yes, it does run Flash (and the Flash ads work very well), but other than that, I didn't see anything it did that the iPad didn't do better. And they STILL haven't figured out that widescreen sucks for this form factor because it makes portrait orientation useless.

That said, it doesn't give nearly the "They have got to be kidding me with this piece of crap" feeling that previous attempts at iPad competitors give (like the Playbook, for example. My GOD what the hell were they thinking? Absolute garbage.)

Part of the answer may be immune system triggers caused by food intolerances (believe it or not). I have Celiac Disease, and it's amazing the array of symptoms that gluten intolerance causes. Not just the commonly known symptom of the immune system attacking the intestines, but it also causes Dermatitis Herpetiformis, which is similar to psoriasis. It actually started me wondering -- if your immune system can attack your intestines, and your skin, why can't it attack any organ in the body, including your brain?

Sure enough, check out this study from the Mayo Clinic. Celiac may be linked to Alzheimer's.

I suspect that food intolerance that cause immune system disease will eventually be linked to other brain issues (that I won't mention, because I don't want to make a controversial point the focus of this post).

Well, two apps interfering with each other is a fair criticism, though I think they shouldn't interfere regardless of multitasking. This sounds more like a criticism of the apps, where they don't give you an option about how they work, especially if there is potential for conflict. Generally speaking, the multitasking runs invisibly, killing off apps when iOS runs low on resources, and that's how it should work. It sounds like you want a "multitasking permission" that would pop up on every app or something like that, which I think would kind of suck. One of the reasons I like iOS is that it does take care of these things automatically and effectively. But I think in the case you cite, it's not a fair criticism of the multitasking.

You've just described how iOS works, and also the criticism that iOS is not "real" multitasking, since it's specifically restricted to only allow certain things to multitask for exactly the reasons we're talking about.

You might want to Google "photosynthesis". Major rivers no longer reach the ocean because we've diverted them for use in industrial agriculture. And yes, that water really does cease to exist as water.

Well... no. You might say that technically the water does "cease to exist as water" since photosynthesis converts water and CO2 into sugar and oxygen. But combustion of the sugar converts it back into water and CO2, so the water is just locked up temporarily until the sugar is metabolized. It will eventually make it back into the water cycle. Water is a very, very stable molecule, and sugar is not (if it was, it wouldn't be a very good fuel).

If you were bitching about memory leaks, that would be a perfectly reproducible problem...

I don't know why the Firefox team can't reproduce it, but before I gave up on Firefox in favor of Chrome, it was trivially easy to reproduce on my system (which used no plugins, by the way). Open a page, close the page. Memory goes up. Open a page, close the page. Memory goes up. Etc, etc. I had to restart FF several times a day because my system would slow to a crawl as memory climbed over 2GB. It was a classic MEMORY LEAK.

Apparently there are people who can get Firefox to work for them, but there are a LOT of people for whom Firefox is a huge fail because of the memory problems. Well, that and the fact Firefox is dog slow these days compared to Chrome, but I digress.

I gave up on Firefox and the memory leaks a year ago. Have never looked back. Chrome is SO much faster. Things pop instantaneously. I don't have to restart my browser constantly because of the out-of-control memory. Do it and be happy with browsing again. Firefox sucks, and you don't realize how much it sucks until you start using a browser designed for speed.

And to those who claim "Firefox works for them," I say congratulations. I don't know why your Firefox doesn't suck, but it sucked on every computer I've run it on. It probably has something to do with the sites I visit that you don't.

So let me get this straight. You say that 100% of music is crap or uninteresting, yet you claim that some other non-musician can take the crap, "remix it," and suddenly turn it into good music? (If they were musicians, they would create their own original music)

I agree with you about modern music, which is basically the equivalent of paint-by-numbers by sound engineers, but your point is absurd.

I'm guessing you're talking the bay area / silicon valley? Your vision is distorted by the huge demand in that one area. Open an office out of state (or even "normal" parts of California) and you'll probably do better at finding people at reasonable rates.

I agree with many of your quirks, though you may be unaware of a few mitigations:

1) You can declare variables in function parameters as 'array' or specific classes, so that is some amount of type discipline.

2) You can get somewhat of a 'use strict' by doing: "error_reporting(E_ALL | E_STRICT)". It's not perfect, but it's better.

3) Error reporting can be improved considerably by setting up your own error handler using 'set_error_handler' and 'set_exception_handler'. Your error handler can also translate normal php errors into exceptions (one 'gotcha': make sure you check the function error_reporting() before throwing an exception, for when '@' operator is used). I have some boilerplate that I bring along to new projects. It displays error detail, back traces, and emails me upon errors. The one thing that still sucks is that you can't capture certain fatal errors, like syntax errors.

So yeah, PHP does have legacy baggage, but at least it gives you ways to somewhat escape the baggage.

I'm actually kind of curious why you "ugh" PHP. I've been doing a lot of PHP programming lately, and I have to say, as of PHP 5.3, it's evolved into a pretty decent language. 5.4 is even better (which I unfortunately can't use yet). Yes, it has its legacy quirks (0 == '' comes to mind), but then, what language doesn't? And PHP (surprisingly) destroys Perl when it comes to speed, especially string manipulation. Yes, PHP in the past was pretty brain damaged, but what do you specifically dislike about the modern language?

I'm not saying PHP is a *great* language, but you know what, it's far better than it used to be, and it's almost pleasant to use these days. I'm reminded of a (paraphrase) quote regarding computer languages: "The only languages people don't bitch about are the ones that no one uses."