Does anyone else find this disturbing?
Well, I've been running Macs as my primary office automation/desktop (vice development) machine for 29 of the last 30 years, and haven't had these problems. And I routinely get 5 years out of my home Macs (and between 3 and 4 years from the corporate machines.)
Your mileage may vary.
Microsoft, since its only product is software, has to go to great lengths to protect and extend that property base. "Extend" here is Googly data mining.
Apple, on the other hand, makes money by selling you the hardware. The protection is the physical ownership of the device. You might not believe Apple when it says "we don't want your personal information", but you have to respect that they're not depending on either data or software to make the great majority of their revenue.
This may not be a popular opinion, but I trust Microsoft more than Google, Apple -way more- than Microsoft, and the NSA more than any commercial company.
The best single book I know to get started in the hobby is Dave Frary's "Pennsylvania Railroad, Middle Division" which you can buy as a downloadable PDF here http://www.ebay.com/itm/Pennsy...
There are good videos on YouTube. Dave Frary also has some good quality DVDs on his website, http://www.mrscenery.com/
Finally, don't buy a cheap locomotive! There's nothing more frustrating than getting everything set up and then having your loco break.
dave (in the hobby for almost 50 years...)
The patent says that data could be sold. It's a substantial leap to say that Apple is currently selling data (independent of this patent.)
There's a difference between 'having their own Ad agency' and 'selling information'. Do you have anything to back up your claim that the Apple Ad agency is selling data?
to distract us from the Invasion of Texas now going on ("Jade Helm 15")
It was very easy to set up specific privileges for specific users/classes of users. I haven't seen anything else come close in 35 years in the business.
I also think VMS was the easiest system to administer, including a well thought out integrated help system that had the right answer for your question with minimal fuss.
The mail hosting companies are particularly delinquent in not making damn sure this is done for every "mom-and-pop.com" they host. If you're not a tech person, but run a small business doing something else, the ins and outs of this kind of thing is what you -should be getting- from an outsource mail service.
With the increasing growth of outsource email, it's getting really hard for spam detectors to distinguish between real spam, and email sent on behalf of one company by some outsourced mail/customer contact management company.
Here's the technology my ISP uses: http://www.escom.com/ (Disclosure: The developer is a friend-of-a-friend of long standing.)
I've advocated (including to my senator, Warner (D) of Virginia, a former telecom executive) that the FCC should require changes to make CallerID Verified. By this I mean that the Telco/switch has to verify the CallerID (e.g. using payment data?), and mark the CallerID information as either verified or suspect. This would not solve the problem, but would, I believe, help both consumers and Law Enforcement.
As long as spammers can forge CallerID, we won't be able to depend on CallerID to screen calls, and DoNotCall registry violations will be much harder to enforce. "Brigitte from Credit Card Services" calls usually have a City/State CallerID value, rather than the name of an individual or organization. But I get some legitimate calls (e.g. my dog's oncologist) that also show up as City/State. (I know to answer calls from Vienna, VA - at least until the Spammers start forging local CallerID values...) My former employer removed its telephone number from the CallerID information, I know if I get a call from "732" (New Jersey area code) that it's most likely one of my former co-workers.
But recently I've been getting Spam calls on my cell, usually (but not always) the CallerID says "unknown". Until this month, such calls were limited to the Land Line (and this is the single strongest argument for ditching the land line.)
ONLY if there are tests to catch the problems that exist in the earlier version!
Either (a) there was a test contemporaneous with the faulty component that wasn't run; or (b) a subsequent fault was discovered, a test for that fault is developed, and that test is subsequently associated with that component (version).
Testing is no cure for bad design or bad coding, which are the -root cause-. The specific design and code techniques to prevent vulnerabilities need to be better communicated and enforced (by open source code reviewers, as well as commercial developers).
That's not to argue testing is unimportant. But it's not the root cause of vulnerabilities, and it's not clear to me that we know how to test for a lot of vulnerabilities.
In my (limited) experience, when I've had a significant tech problem, my goal is to work with the Tier 1 guy to run quickly through his/her troubleshooting script and to get a hand-off to Tier 2, more expert support. Sometimes that's the level that can authorize on-site repairs, changes to routing tables on their end, etc. The other option, particularly if this isn't a residential/consumer account, is to talk to the sales rep. A good sales rep (not always an oxymoron!) can sometimes open doors for you from the inside.
And for what it's worth: I've had the least expensive business grade service from Cox (Northern VA) for over 10 years, and generally have been very pleased with both the reliability of the service and the support when I have had problems. The only real issue I had was "left hand not talking to right hand" when the residential cable installer was unaware of the business internet connection, and disconnected it. The second time that happened, I ran after the guy's truck, demanded he call his office to confirm I had both services (on separate contracts) and then reconnect the line. That same installer came out on a subsequent call and remembered that incident. (I was a bit distraught, since I was getting ready to leave to go to my mother's house after she had a very nasty fall, and basically said, "I don't need to be dealing with this s**t right now!")
System going down in 5 minutes.