When Apple’s Progress Hurts
UPDATE! The complaint in this post has been satisfied. See ….
A Mac doesn’t work with your stuff when:
Your office has a Windows 2003 file server with AppleShare enabled and you just bought a new Mac with OS 10.7 “Lion”.
Why does your Windows server support that old AppleShare protocol anyway? Maybe because you have 20 thousand files that were named and saved when AppleShare was Apple’s premier method of networking, and you need to see the special characters that help you identify them.
Or maybe your office firewall allows the AppleShare port to reach the server from the outside so you can do some work from home. The AppleShare port is more secure than Samba, so the easy way to connect without a lot of expensive or complicated VPN solutions is by using AppleShare.
But now you have Lion and suddenly you can’t connect to your Windows file server using tried and true AppleShare. Those familiar steps of selecting Connect To Server and typing afp://server.myoffice.com now result in the following accusatory message.
Your server does not support this kind of connection.
So it’s my server, not the fact that Apple deleted DHCAST128 in their latest product line?
Apple’s cheery claim that a Mac works with your stuff has a long list of caveats. And the solution is always that you must fix your stuff. Here’s one community support thread.
Question: Why use a Mac if the important tasks must be done in a command line?
I read every possible article and tech note about Lion before I advised clients to go for it. No where did I find warning that the so called improvements would force costly upgrades and changes to procedures.
I predict that Apple will gleefully tell consumers that their change is a good thing and you’ll be better off if you change your whole routine to their standards. It’s only money and time right? That shouldn’t stand in the way of progress, should it?
But is this progress? Is it better? At some technical level that only matters to Apple is it probably better. I don’t see what’s better about losing weeks and months of productivity while solutions are deployed.