I also supported the Macintosh Platform at Netscape (HUGE Macintosh house) from 1996-1998. A good portion of the time we ran into a tough problem on the Macs there (by then we had hard drives), our Mac Lead (which I was not) - had us do a "Fresh Install" of the operating system. That pretty much always resolved the problem, but seems kind of invasive nowadays.
I sometimes think we view Mac History through rose colored glasses.
I will agree with you - that damn beachball is annoying. Though, I am happy to say, that as of 10.7.4, it probably only spins for about 5-10 minutes of my day now in aggregate, as compared to the 20-30 minutes a day back in the 10.7.1 era.
Everything with computers is a trade-off. I'm happy to make some trade-offs and forgo whatever Cupertino is hawking in order to have flexibility and speed like the "good ole days".
"Certified UNIX". Pure marketing. Apple has the budget. There are vastly better UNIX implementations (from which Apple has borrowed copiously) that will never be certified. Go figure.
From where I sit, the most talented coders always seem to hold the POSIX specifications in spite. They do not like them. OSX is proof that they are not being unreasonable by taking that view.
To be clear, I'm not endorsing GNU/Linux. That is a whole 'nother story of UNIX gone bad.
Like who? And what has Apple copied from them?
http://netbsd.org http://freebsd.org http://openbsd.org http://dragonflybsd.org
They all borrow from each other. They even borrow from Apple sometimes.
As for what has been copied, you simply need to read the source code.
Instead, you're saying OSX, which is BSD-based, borrowed elements from...BSD-based projects?
Wow. What's next? Are you going to call out the Kubuntu team?
The ST has 1 8Mhz processor and 1M RAM and a floppy drive. The Mac has 4x3Ghz cores and 8G of RAM, HD not SSD like that's an excuse. And remember we are talking about simple GUI updating tasks here. There is simply no getting around that the interactive parts of OSX are appallingly badly written. Processing a mouse click and drawing a menu, for crying out loud!
And your machine gets more and more powerful. That comes from the hardware. Software does not add more power. It drains power.
But you will not likely see much of the gains from Moore's Law as a home user; you only see "new" software. The software industry will be the ones who get the benefit of hardware advances. They will promptly usurp all the gains for themselves to make their bloated software capable of running. Writing power hungry programs is perfectly acceptable (I love writing code) BUT _forcing_ people to use it is not cool. Users are not often given a choice to keep using "yesterday's" software (even if it still works). Even if it would let them see the gains from Moore's Law. That is a travesty. Keep staring at the beachball. Life is good.
We've had decades to observe software development and it's clear that software does not have an equivalent to Moore's Law.
Let us buy the Apple hardware without the Apple software. Let us install our own software if we so choose. Now, behold as people try to argue against this. But they are only arguing against options and choice. What is the harm in giving people the option to install their own OS? If anything without the Apple brand is so terrible then surely no one would opt for it. So no harm done. You never know, they might actually be able to sell lots of hardware this way. "Average consumers" are not the only ones who spend lots of money on hardware.
Apple has taken a decent system (free UNIX) and ruined it. They have made it unusuable for anyone who has any idea of how fast computers SHOULD be.
Imagine if the car industry worked like this, if 3 years after you bought a car it wouldn't work quite right with the only fuel you could buy, and spare parts were impossible to obtain, and the engine compartment was welded shut!
Right now there are 257 tasks running on my Ubuntu box. I don't recognize half of them.
It feels we are slipping backwards.
If you need one, I'm happy to send you a UNIX (or simple instructions on how to build one) that does not have the complexity of Ubuntu but runs just as fast and does all the same stuff, sans the gratuitous GUI's. You can always add GUI layers later if you want them. My guess is you won't once you see how much faster things are, and how few processes you need to be running at any given time.
Do I have to prepay postage? Should I send you a self-addressed envelope?
In Apple's failings, there is immense opportunity.
Follow the bouncing beach ball...
My favorite part is when he receives simple, straightforward advice from Apple on how to fix his iPhone issue, but he chooses to ignore it. Instead he scours the web for alternatives, and spots one suggestion that is applicable to jailbroken phones.
"Are you frickin’ kidding me? I have to jailbreak my phone to fix this problem?"
Uh, or you could just try any one of the four easy solutions you've been offered so far.
But that would make way too much sense, so he continues his search. He ends up at iphonefaq.org, a site that "looked pretty official." Are you freaking kidding me?
Finally, after hours of searching, he arrives at this gem:
"The only option that was relatively straightforward and seemed to work, according to many forums, was to restore the phone."
As in, the original solution provided by Apple's tech support. Apparently it's Apple's fault that he can't follow directions or readily accept simple solutions. I can't go on, I'm getting dumber just reading this.
Now what?
If a warning light on my car's dash turns on, I might look for a fix online. But if someone in a forum suggests I drive my troubled car off a cliff, I'm not going to write an angry rant accusing Ford of making me drive my car off a cliff.
I'm also not going to navigate to some amateurish-looking website that's obviously not affiliated with Ford, and claim that I can't tell it apart from Ford's website (and imply that Ford is somehow responsible for my confusion).
And if I can't fix it myself, I'll bring the car in for servicing, rather than writing a linkbait article speculating about what the repairman might tell me. (In fact, if the phone is a year old and it has a legitimate issue, Apple might just hand him a new phone... I find that scenario more in line with my own experiences, but we'll never know, since he couldn't be bothered).
> Unfortunately, beyond jailbreaking it there was no other worthwhile solution.
Really? Because he listed a bunch that all seemed more worthwhile.
simple, straightforward advice from Apple on how to fix his iPhone issue, but he chooses to ignore it.
'Oh, your phone has 2/3 of the storage taken up by cruft because our OS doesn't work properly. Delete everything on the phone and start over. Have a nice day!' This is answer may be "simple and straightforward" but it is not "acceptable."soon: "That model is 9mo old and Apple gave you a simple, straightforward answer: buy a new one. Why are you still complaining?"
> I have to jailbreak my phone to fix this problem?
Clearly, that's not his only option.
I've watched people struggle like he's describing. Too many upgrades. Too many authorizations. Too many restrictions. They are jumping through hoop after hoop just to do basic stuff. If they are young they probably don't know any better. But for anyone who has been around, this has gotten to be a joke.
If you have stuck with Apple over the long haul, then you remember what it was like before OSX. When OSX was first introduced you had to upgrade your Mac hardware just to run it or it would be dog slow. Then it got better over time as we all upgraded but it has gradually become more and more annoying. How many people are staring at a spinning beachball at this very moment? Trying to appeal to PC users, all the Mac vs PC nonsense. Then trying to lock down people's music and other files and make them "subscribers", like they are some sort of media licensing company. Apple is no longer an alternative to the typical computer hassles. They have become a primary source of them!
But only if you have been using Macs for many years can you see this. Noobs and fanboys are not going to notice. They will wait minutes for their Mac to boot and stare endlessly at the beachball and accept that this is "fast, start-of-the-art computing".
While noobs suffer through iPhoto staring at beachballs, I will boot in seconds and process my photos, running in a background process, in half the time, using a more traditional UNIX without the Cocoa cruft. No hassles.