IT in the Ad Biz:

Macintosh

Mar 28 2008   7:01PM GMT

Mac vs. PC - Round 1



Posted by: John Wilder
Microsoft Windows, Macintosh, IT department

It’s about time that I got around to this one, and if any of you have been wondering which side of the argument I might come down on, you might be disappointed to find out that I sit firmly on the fence on this issue. I’m a firm believer that both platforms deliver on their particular strengths, and both are outstanding tools which are helping us all to become more productive. If I didn’t believe that, why on earth would I have spent the past 15 years purchasing and supporting both platforms?

However, don’t mistake my middle of the road stance for a lack of conviction, because I do have some very strong feelings about the issue itself - in fact, I have a huge problem with the argument itself. I’ve never seen a real definitive study of our industry, but I would suspect that somewhere around 75% of advertising firms operate the same way that we do, supporting both platforms. Of the remaining 25%, I would venture to guess that the majority are Mac-only shops, with a small handful of PC-only shops.

I’ve heard all the arguments. “The Mac is a toy.” “PC’s crash all the time.” Take your pick, because you can find plenty of people out there willing to scream that their favorite system is the best, and the other system is garbage.

The latest round of Mac ads certainly don’t help, and I cringe every time I see them. Yes, they’re clever. Yes, they sell computers. But are they accurate? In my opinion they’re not even close to the truth. Apple, as well as most of the Mac evangelists, are still making arguments against Windows 98. Sure, they talk about Vista in the ads, but if you want to discuss stability and security, it’s difficult to deny that Windows has improved considerably.

I’ve been running Windows servers for over 10 years, going all the way back to Windows NT. The platform has been remarkably stable. Have I seen blue screens - certainly I have, but they have been few and far between. I have Windows servers which have run for years without anything other than a reboot for updates. At the same time, I’ve also seen plenty of my Macs crash - perhaps even more frequently than our PCs. I’ve heard the argument that the reason our Macs crash is because they’re working harder than our PCs. It’s not easy pushing around all those graphics files. No, it’s not, but by the same token it’s not easy doing what an Exchange server does - and they don’t crash. Earlier versions of Windows have been full of security holes, but here’s an interesting article on Mac security which appeared today - http://www.crn.com/hardware/207000418.

Even in writing this, and attempting to defend one platform, I find myself falling into the trap of bashing the other. That’s not my intent, but it’s nearly impossible to avoid the trap. The Mac has proven to be a superior machine for working in a graphics intensive environment. I’ve seen the benchmarks, and these machines truly are tuned for doing what they do best. I would not even begin to entertain the thought of switching.

I buy Macs. I buy PCs. I take the attacks from both sides personally. If the Mac side is correct, then I must be foolish for purchasing PCs. If the PC side is correct, then I must be foolish for purchasing Macs. The fact of the matter is, both sides are wrong. Both platforms serve their purpose, and they serve it well. I woudn’t even compare this argument to Ford vs. Chevy. It’s more like arguing that sports cars are better than pickup trucks. They serve different purposes, and they both do their job well.

I’m sure I’ll return to this topic again and again, and I welcome your opinions no matter where you sit on the issue. I’m going to try to take the high road and avoid bashing one platform in defense of the other, but I also plan to speak openly about the shortfalls of both systems. We’ll see how it goes.

Mar 10 2008   12:19PM GMT

Office (and File) Moves – Part 2



Posted by: John Wilder
Macintosh, IT department

Perhaps the single biggest issue we encountered during our office move last weekend had more to do with moving files than it did with bringing a new office onto our network. Furthermore, this particular issue was one which we’ve encountered before, and it was also one for which we didn’t have a readily available solution. In a nutshell, we ran into major problems attempting to move or copy Mac files from a UNIX server onto our new network and a Windows server.

I’ve run into this problem in the past, and it’s never fun. The problem lies with the ability of Macs to use characters not allowed by Windows, characters such as the slashes, bullets, and parentheses. When you run into hundreds or perhaps thousands of filenames extending deep into many levels of subfolders, it’s not an easy thing to clean up. Attempting to move or copy the files from one platform to the other results in either failure or truncation of the original filenames, neither of which is an acceptable outcome.

In our company, I’ve been lucky enough to have a Studio Department which has recognized this issue and taken steps to correct it. When IT has attempted to police this problem in the past, we’ve met with limited success. When the policing effort comes from within, as is the case with our Studio Department which is made up of hardcore Mac users, the other users tend to listen. As a result, we’ve pretty much eradicated the odd characters internally, and this hasn’t been a huge issue for us – which may also be the reason I didn’t think of it prior to this move.

What I wish I had done was send our Studio folks in ahead of our move to explain our internal processes, especially regarding the file naming conventions, and to encourage a general cleanup of files prior to our move. If we had done this, we would have had about 30 days to prepare, and we could have at least had the current jobs named correctly and ready to move onto our new systems. The solution we ultimately came up with involved maintaining the old network, connecting their old server to a Mac and a PC in a common area. We asked the users to do the cleanup of the filenames, and then utilized USB flash sticks to move the files onto the new network.

In any case, it was a valuable lesson re-learned, and just another one of those issues we can sometimes take for granted when we live in a cross-platform environment.