I get asked this a lot. For the Mac, it's pretty simple for me:
Windows: Has a decent/cohesive UI but a crap OS underneath Linux: Has a great OS (unix) underneath but a crap UI (C'mon admit it, it sucks and is not cohesive) Mac: Has a good/cohesive UI and a great OS (unix) underneath. Best of both worlds.
For Apple products in general. 1. Stuff just works. Got my first iPhone, plugged it into my Mac, Sync'd it with iTunes. 30 seconds later my phone "pinged" that I had new mail. Everything was there. 2. It's much more than the device itself. My mom has a Mac and needed help with various things. Made a genius bar appointment and they helped he with everything and didn't make her feel like an idiot. "How do I move things from my flash drive to my Mac?" "Oh, here let me show you."
Also, believe it or I think they (most times) have a good sense of the way things should be.
In the beginning, Android users would say how stupid it was to have this "walled garden" as they can install from anywhere. Ends up that installing from anywhere is might not be such a great thing. Then they said how stupid it was that there was only one version of iOS and many flavors of Android. Ends up that fragmentation is not such a great thing.
I say use what works for you. Working on a Mac with a trackpad and using spaces fits how I work very well. If I need to write some documentation, I use MS Word.
When I worked at a defense contractor their policy was 1 hour per day for being on call, minimum of 1 hour if you got called and had to do something, and 4 hours if you actually had to drive to the office to fix it.
Obviously if you got called multiple times for the same problem (i.e. you didn't fix it right) it all counted as one "call".
Since most people were on a salary, it ended up being comp-time instead of pay. I was lucky, I was classified as a "tech" so I got time-and-a-half for all the hours.
Slashdot Mirror
I have an Apple //e sitting next to me tricked out with solid state storage and an ethernet card.
*puts his nerd card back into his wallet*
I get asked this a lot. For the Mac, it's pretty simple for me:
Windows: Has a decent/cohesive UI but a crap OS underneath
Linux: Has a great OS (unix) underneath but a crap UI (C'mon admit it, it sucks and is not cohesive)
Mac: Has a good/cohesive UI and a great OS (unix) underneath. Best of both worlds.
For Apple products in general.
1. Stuff just works. Got my first iPhone, plugged it into my Mac, Sync'd it with iTunes. 30 seconds later my phone "pinged" that I had new mail. Everything was there.
2. It's much more than the device itself. My mom has a Mac and needed help with various things. Made a genius bar appointment and they helped he with everything and didn't make her feel like an idiot. "How do I move things from my flash drive to my Mac?" "Oh, here let me show you."
Also, believe it or I think they (most times) have a good sense of the way things should be.
In the beginning, Android users would say how stupid it was to have this "walled garden" as they can install from anywhere. Ends up that installing from anywhere is might not be such a great thing.
Then they said how stupid it was that there was only one version of iOS and many flavors of Android. Ends up that fragmentation is not such a great thing.
I say use what works for you. Working on a Mac with a trackpad and using spaces fits how I work very well. If I need to write some documentation, I use MS Word.
To each his (or her) own.
If it doesn't have a touch screen, then I call "Fail!". Unless they've done a lot of work on the interface.
I've installed Android x86 on a netbook and it is horrendous with out a touch screen.
Android, since it's roots are for mobile phones, really wants to be touch driven. Without it, I'll pass.
I've always enjoyed using this on any Linux box:
$ who mom likes
When I worked at a defense contractor their policy was 1 hour per day for being on call, minimum of 1 hour if you got called and had to do something, and 4 hours if you actually had to drive to the office to fix it. Obviously if you got called multiple times for the same problem (i.e. you didn't fix it right) it all counted as one "call". Since most people were on a salary, it ended up being comp-time instead of pay. I was lucky, I was classified as a "tech" so I got time-and-a-half for all the hours.