consumer reports broke the whole antenna-gate thing specifically so that noone would suspect that they were really paid Apple shills.

What's it like to be an idiot?

Burn.

Tesla cars are allowed on the roads in Iowa. Iowa will even register a Tesla car and issue you license plates, etc. They've passed every safety test & regulation that any other car has.

You just can't *buy* a Tesla car in Iowa because of dealer-sponsored 'franchise' laws. It seems pretty weird that those laws cover giving out test drives--I'm sure Tesla's lawyers will look into that.

OSX is my favorite, second to Linux. But honestly, it's isn't that close.

That's the whole point of Apple's walled garden and their policy on multi-tasking. Obviously Android has gone a different route and I can't fault them for doing so--but it isn't an unsolvable problem by any stretch of the imagination.

iPhone users, by and large, couldn't care less what kind of phone you use. The world needs more options and fewer snobs.

nt

where do you think the money came from that they are using to buy stock back?

It has nothing to do with perfection at any level and never has in the history of mankind, ever.

Apple removed a sentence from their quarterly filings and obviously this is a sign of imminent fascist genocide.

Smart people are some of the stupidest people I've ever met.

nt

Apple will start killing puppies and then charge you a fee to stop.

is better if I'm not buying a new smartphone every 2 years?

What's it like to be an idiot?

It has nothing to do with perfection. It's about statistics.

This is probably something that is well understood by the engineers who are building robot surgeons (and maybe even by those building driverless cars), but it certainly isn't well understood by the overwhelming majority of software engineers and it's just a matter of time until the unwashed hordes of C++ monkeys are unleashed unto critical systems.

Bridges aren't designed and tested by "trial & error"--if they were then half of them would fall down within a few weeks. Neither are buildings or pacemakers or computer chips.

There are some scary problems with how [many if not most] software engineers see the world which don't bode well for a world where software can kill:
(a) by and large they've had essentially no exposure to any method of verification other than "trial & error"
(b) they have insufficient reverence for cause and effect because most of their bugs have really low cost (as in, nobody dies)--therefore they aren't mentally trained to make disciplined decisions.
(c) arrogance: unlike every other kind of engineer, software engineers rarely encounter the boundaries of their knowledge. A civil engineer knows when to call a materials engineer, a mechanical engineer knows when to talk to an industrial or chemical engineer, but a software engineer spends their entire lives inside a carefully constructed virtual world where they can't really do that much damage.