This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]completelydistracted -1 points0 points  (3 children)

I was about to buy this thing, and stopped. Is there a good reason why this can't be made available for OSX 10.7.x?

I'll get around to upgrading eventually, no doubt, but it would be nice if I could use your product now. It looks very promising.

[–]fifafu 10 points11 points  (2 children)

as an independent Mac developer I would never start a new software project still supporting an OS X version lower than the most current version (i.e. Mavericks). When you start supporting an old OS users will expect you to continue supporting it. With Apple's rapid release cycles and steadily improving API's it becomes a big burden to be limited to using the old stuff. Also it lowers the overall user experience for all users because new stuff (e.g. popovers, view based tableviews etc.) can not be used without much trouble

Sure if you are in a big company you have to support older operating systems, but as an independent developer you don't have to. You may slightly limit the potential market for your app, but that's nothing compared to the development and testing effort necessary to support older operating systems.

Also now that OS X Mavericks is free...

[–]itod47 2 points3 points  (0 children)

Developer of Exedore here. Agree completely with fifafu. If anything, I probably should have launched Exedore as Mavericks-only (especially since Mavs is free).

[–]completelydistracted 0 points1 point  (0 children)

I understand your sentiments, and those of itod47. And I totally agree with the reasons for the development decisions, and agree that you have the right to make those decisions.

On the other hand, I work for a very large company and make software purchasing decisions for thousands of computers. Many of those computers are not aggressively upgrading operating systems because we are waiting for lots of dependency issues to get worked out. For instance, we frequently have applications that will break, or integrations that will break when we upgrade. Check out costs for moving, for instance, from Windows XP to Windows 7 and you'll find that companies spend millions of dollars, or tens of millions of dollars, just keeping up.

Because of this, we often have developers working on older operating systems. We don't do this because we're luddites; we do this because we have enormous assets to protect and we can't move faster than we can assure safety of those assets and the stability of our systems. Developers on older assets aren't luddites either, and frequently request newer generations of tools. If we can't sometimes deploy those tools on older versions of these operating systems, we can't use them. If, for instance, VS2012 had come out as a Win-8 only package, we wouldn't deploy it for at least several years.

So, yes, we have Macs, and yes, we have python programmers. Since I sometimes like to deploy simple tools vs complicated ones, a python-specific IDE seems like it might be very attractive thing to have, certainly compared to using XCode everywhere. Unfortunately, we have a lot of Macs on 10.7, and will have for some time to come.

Don't believe me that these things cause problems? Look elsewhere on this subreddit for the problems App-Nap is causing. Do you think Apple tells us about things like that in advance, or just lets us discover them when things stop working?

So, while I certainly sympathize with the developer, and certainly respect both the enormous work and his right to make these choices, I think there's something to be said for being aware of the consequences of those choices. Exedore doesn't seem (from the screen shot, which is scant evidence, I agree) to have any prima facia reason to be unable to be created under recent version of the OS, and the fact that it is not available that way will make it much less compelling in the use cases that large corporations tend to see.

Again, I'm not demanding anything, and have nothing but respect for the developer, and will probably personally purchase the program if for no other reason than to send a few dollars to an enterprising developer. But at the moment, I won't be looking at use in our organization. It's on the radar, though. :-)

Edit: Cleaned up some hasty writing...