![]() ![]() It was stellar service and I was quite impressed. Adam fixed the bugs that I had encountered, and explained what I needed to do to regain the ability to undo. However, much to Adam Tow’s credit, I must say that, within a week of the initial release, all of the problems were solved. There were some serious bugs, and there seemed to be a loss of functionality, especially in the ability to undo a message move done by MsgFiler with a simple command-Z within Mail. MsgFiler had indeed become a stand-alone application and was no longer a mail extension. ![]() When MsgFiler 3.0 came out on the Mac App Store, I went ahead and purchased it, but the first impression was not good. ![]() Could he really sell a Mail extension/bundle through the Mac App Store? Would it work as well as the current version did? ![]() So, when Adam Tow, developer of MsgFiler, sent an e-mail to everyone back in February 2011 announcing that he would discontinue his current product and start selling a new version of MsgFiler exclusively through the Mac App Store, I became a bit worried. (I usually am, but they won’t take my bug report seriously until I verify this myself.) (Such extensions go in a folder called “ Bundles” inside your home library’s “ Mail” folder.) I say sort of supported, because whenever I submit a Mail bug report to Apple with a crash log, the first thing that the engineers ask in the reply, in a very terse tone, is that I disable my Mail bundles and try to reproduce the problem without them. We are talking about a third-party utility that is really useful, no matter what Apple thinks or says.Īnyway, back to MsgFiler… The original MsgFiler that I purchased last year and became an avid fan of was a Mail “bundle,” which is some kind of extension that is sort of supported by Apple for Mac OS X’s Mail. We are not talking about a third-party hack that unnecessary wastes CPU cycles to display trendy useless 3D junk on the screen here. Who is Apple to decide that my use of a tool such as Default Folder X is “bad” and cannot be condoned? I am more than willing to temporarily disable Default Folder X whenever necessary to verify that a bug in Mac OS X is not caused by its presence, but I am definitely not willing to stop using Default Folder X simply because Apple decides that it’s not consistent with its software development philosophy. Jon says that Default Folder X and his other products aren’t going away, but it’s still a concern when the provider of the underlying OS has such a restrictive vision of what its developers and users should and should not be able to do with their computer. I am a long-time user of Default Folder and I simply cannot imagine life without it. I read Jon Gotow’s post about the disappearance of the “ Apple Downloads” section of the Apple web site and its potential impact on Jon’s products. Then Apple announced the Mac App Store, with all its rules and limitations, and I started to worry about some of the vital third-party tools that I use and what they might become in a Mac software industry dominated by the Mac App Store and its staunch rejection of any software that might not be 100% above board in terms of the way it interacts with the underlying operating system. In spite of my initial reluctance (due in part that I had already shelled out some cash for Mail Act-On and didn’t want to add too much to the complexity of my e-mail setup), I ended up purchasing MsgFiler and quickly became a fan of the product. A while back, I wrote about message filing in Mac OS X’s Mail and, in particular, I mentioned the third-party tool MsgFiler and its apparent pros and cons. ![]()
0 Comments
Leave a Reply. |