Labels: australia, beatles, cbc, environment, evolution, holiday, lipglossandlaptops, microsoft, photography, podcast, sex, vancouver, video
John Gruber points to this article about PC upgrades by Marco Arment:
The upgrade market for average PC owners is dead. We killed it. [...]
In 1998, when everyone was happily using long filenames and browsing the internet and playing their first MP3s and editing their first scanned photos to email to their relatives, a five-year-old computer couldn't easily do any of these things.
But what common tasks in 2009 can't be accomplished by a 2.8 GHz Pentium 4 PC with Windows XP SP2 and a cable internet connection—the average technology of 2004? Not much that regular people actually do.
That reminded me of something Geoff Duncan wrote at least five years ago, which I can no longer find anywhere online:
Your average PC user doesn't update anything. They just throw the computer away when it stops working and buy a new one, then don't change the software on it either for fear of breaking something.
Things haven't changed much, but we'll see if enough people need new computers in the next little while to give Windows 7 a boost. Microsoft's new operating system comes out this week.
Labels: geekery, microsoft, windows, windows7
Yup, still on a blog break. So, more of my selected Twitter posts, newest first:
Labels: audio, biology, blog, cancer, chemotherapy, family, flickr, geekery, google, microsoft, movie, music, oceans, photography, sex, startrek, transportation, video, whistler
I finally did get the Zune player working a few weeks ago, and my daughter has enjoyed using it ever since with the same set of songs, videos, photos, and podcasts I first loaded onto it. But she wanted some different stuff, so today I borrowed by dad's Windows laptop again and set about updating the little device.
What a freaking pain! Even though the Zune software was fully installed and working, somehow it had forgotten most of the subscriptions I had set up, and was still slow, scatterbrained, unintuitive, and frustrating. Getting new media on it took well over an hour, since I had to try a couple of different approaches.
I'm a Mac guy, yes, but I've been using PCs for more than 25 years, and even worked for a Windows software developer for almost five of them. Yet every time I have to install or manage something using Windows, my wife and kids know to leave me alone, because it turns me into Mr. Grumpy Boy. The Zune software only compounds the problem—somehow Microsoft, the company that makes both Windows and the Zune, can't get them to play nice with each other. At least not for me.
So I'm reinforcing my original conclusion: the Zune device is very nice, with a pleasant and useful interface. It works well once you have media on it. If some third party (or Microsoft, not likely) made a Mac client to manage it, I'd quite like the little player. But the Zune software you have to use to manage it is crap, and only runs on Windows, which for me makes it doubly crap.
Grr. Grumble. Phht. I'm glad I didn't have to pay for the thing.
Labels: design, microsoft, software, zune
UPDATE: By some miracle (and no, I don't know what I did), one last try at installing the software worked at around 12:30 p.m., and I managed to load on some video and audio, plus podcasts, onto the Zune device. I'm going to transfer a bunch of my daughter's MP3s and let her give it a spin to see what she thinks of the Zune now that it's working, more than 24 hours after I first started trying.
It's been a few years since I used Windows regularly, but as a typical Mac fanboy I do have to ask: do those of you who run Windows regularly actually have to put up with this level of frustration all the time?
Right now I'm staring at the Zune installer program screen, telling me for the fourth or fifth time that it "Can't access Microsoft Update" (I can access it fine by going to the website, by the way). This is on the second computer I've borrowed from my dad to try to install the Zune application. Yesterday I spent something like nine hours (on and off, mostly off, thankfully) trying, repeatedly failing, and then eventually getting the Zune software to install on his older Windows XP laptop. And then, at the end of the day, while the computer itself could see that the Zune player was connected, the software never did, and I could never sync anything to be able to play it.
Having worked for a Windows software developer at one point, I have decent Windows tech-fu techniques, which I employed during yesterday's mess, even creating a new user account before the software successfully ran. Yet here I am again, needing to put the same skills to use once more the next day to get a Microsoft product working with a Microsoft operating system, because yesterday all of my ninja skills weren't good enough to get the music player to, you know, play music.
It's a pity. I like the Zune as a piece of hardware. It's cute, the packaging is nice, it seems well built, the premium headphones are really quite elegant (if bass-heavy). Yes, the Zune design team has tried way, way, way too hard to ape the iPod Nano—the one that's two generations old now, by the way—even down to the "Hello from Seattle" etched into the back in place of "Designed by Apple in California." They've made the hardware as close as they can get to an iPod without getting sued, I think.
The Zune pad that replaces the iPod scroll wheel is good, and the onscreen interface is nice indeed, smooth and useful and (for once) different. What I've seen of it, anyway: I've been unable to do anything with it, not even listen to FM radio, because the Zune (unnecessarily, I think, like the iPod too) needs to be set up from a computer first. Which is my whole problem.
If you buy an iPod, is setting up iTunes on Windows this bad? I've never done it, but I may try just to see how the experiences compare. If it is, I'm sorry, and it's a wonder that anyone ever uses a portable music player. At this point, if I'd actually paid money for the Zune, I would have returned it by now, since for the past day it has been an attractive electronic paperweight, and not a sufficiently heavy one at that.
But for now, as I've been writing this rant, I've used one of my Macs to download the full Zune installer package and move it to my dad's XP laptop using a memory stick. It seems to be installing. Perhaps by the end of this paragraph I will know if the Zune software can see the Zune player, and maybe let it play some music or videos...
Nope. "INSTALLATION FAILED. Could not write the Zune Launcher to key \SOFTWARE\Microsoft\Windows\Current Version\Run." What a lovely experience, and waste of my time.
Labels: design, fatigue, ipod, microsoft, software, zune
Yeah, I got the Zune today, but no, despite efforts all fricking day long, I have not actually managed to play any audio or video on it yet. So here are some photos:
Labels: audio, linkbait, microsoft, zune
It looks like a few people are getting those free Zunes from Matchstick I mentioned recently. Mine would have arrived yesterday, but I was off at the clinic, and again today, so FedEx Ground is dropping by again tomorrow.
Honestly, other than the Zune itself, I'm most interested in the "premium headphones" this promotional one seems to come with. I've always found Apple's stock iPod headphone earbuds remarkably lame. On the other hand, these premium earbuds don't come stock with the Zune either.
Labels: audio, headphones, ipod, linkbait, microsoft, zune
I was a bit surprised to be contacted by Matchstick, a Canadian "word of mouth marketing" company, yesterday. I figured after some of their missteps a couple of years ago, they might have gone out of business—but instead it seems like they might have learned a thing or two and survived.
They've been contracted by Microsoft to find bloggers and other types like me to evaluate the Zune media player, software, and online marketplace, which has finally become available in Canada after its U.S. release almost two years ago. I (and Chris Pirillo) had a chance to play with the first-generation Zune—yes, the brown one—briefly in Seattle before that original release, and I was impressed with the hardware and user interface. At a recent trip to Best Buy, I also liked the fun but very un-iPod-like approach to the Zune onscreen user experience, despite the extremely iPod-like form factor of the device itself.
But I haven't had a chance to work with the Zune software at all, and reviews of that over time have been mixed. Matchstick will be sending me a black Zune 8 to try out, so I'll find out for myself. But I'll either have to borrow a Windows PC from someone, or install Windows on my MacBook, to get it to work—there's no Mac support, alas.
But with luck I'll be able to find out whether our Zune subscription links at Inside Home Recording actually work. The little Zune should arrive next week sometime. Maybe I can photograph it with the new/old camera.
Labels: audio, gadgets, ipod, microsoft, zune
I used to teach courses about Microsoft Word. Stuff like this (via John Gruber) is what made me stop.
Labels: apple, macosx, microsoft, publicspeaking, software
I summarized my opinion of the proposed $45 billion takeover of Yahoo! by Microsoft in my comment on Robert Scoble's post:
I think if the merger happens, it will take ages to bring the two companies together, Yahoo!’s best people will bail out, and by the time the smoke clears, Google will have lapped Yahoosoft/Microhoo several times. Bad for both sides, and in the end for users, in my opinion.
Then again, I know nothing about running a business. These are just my instincts.
Here's what some other people had to say:
Labels: geekery, google, microsoft, money, web, yahoo
A bunch of stuff I've been accumulating over the past few months:
Labels: apple, backup, band, blog, environment, extremesports, food, google, linksofinterest, macosx, microsoft, music, publicspeaking, web
Robert and Dave are right. Macs don't work properly all the time. No personal computer does, or ever has, unless you get it into a working-perfectly-for-a-particular-task state and then don't change anything. Sound engineers and video techs who use their Macs (or PCs) to make money know that, which is why once they've got a system wired up and configured and working, they lock it down, keep it off the Internet, and avoid even innocuous things like bug-fix updates until they have a bit of spare time to tinker if something goes wrong.
We Mac-heads enjoy all those "I'm a Mac, I'm a PC" ads, but we know they lie. The new Mac OS X 10.5 "Leopard" breaks things just as Windows Vista does. People have fun with their Windows PCs (seen all those games?). My in-laws had their iMac lock up after playing a YouTube video yesterday, but they managed to sort it out without my help. The brand promise Robert talks about of Macs "just working" is true a lot of the time, but not all the time—and not in the way we expect of our cars or fridges or TVs or stoves or pacemakers or jet aircraft or roadways or electrical grids or dialysis machines.
It's also true that, despite the problems—and I've had a few—I enjoy using my Macs, and do find they stay out of my way, more than I ever did with any of the Windows or Linux (or DOS or Unix or Apple II or PDP-11 or mainframe) computers I've worked with over the decades. In part that's Apple's doing, in part it's the hard work of the people who design the Mac software I like, and in part it's my familiarity with the platform, because if I have a problem, I also usually have some idea how to fix it. (After working with Windows a lot, it's true for me there too, but not as much.)
There are reasons people like me have stuck with Apple machines even when they weren't very fast, or very cool, or even with any apparent future. It's not just running with the underdog either. I'm not impressed with some of Apple's behaviour recently in markets where it now dominates, such as the iPod and online music and video sales. But it is no shock: Apple has always spun its stories, and has always had a streak of hubris—a pretty wide one at that. I don't think many people would like a computing world where Steve Jobs beat Bill Gates in the early '80s.
Yet when I open the lid on my MacBook to get something done, it generally helps me do it, and seems friendly in the effort. Even if you don't see it as much anymore, the smiley face is still there in spirit.
Labels: apple, davewiner, microsoft, robertscoble
Microsoft has been diligent in releasing updates to its Office 2004 suite for Mac, largely to address security vulnerabilities. That's good. But their updater software sucks. Here's why:
The latest update is version 11.3.9. It turns out that I hadn't updated since 11.3.4 or thereabouts. Now, you'd think that the 11.3.9 update would update any version of Office to the latest version. Nope, here's what I had to install today:
If you look at those screenshots above, you'll notice that only one update appears in Microsoft's AutoUpdate software at a time. That's right, I had to run the updater, apply the version 11.3.5 patch, quit that, run the updater, apply the 11.3.6 patch, quit that... and so on.
I fear to think how long it would take if I had to reinstall from my original-release Office 2004 (11.0.0, I guess) disc. I suppose I should be glad I didn't have to reboot each time!
UPDATE: I forgot to link to my previous rant from last year about the even worse procedure I went through with Adobe Reader.
Labels: design, macosx, microsoft, software
I like what the Mozilla Foundation developers are doing with the user interface for the upcoming Firefox version 3 web browser: matching the interface elements to the operating system:
While Firefox looks good now...
...sharing a general appearance with other applications in Windows or the Mac OS will make it a better experience, and I think it's a good investment of developer time.
Labels: apple, design, firefox, macosx, microsoft, software, web, windows, windowsvista, windowsxp