On 01/03/2016 6:07 AM, [email protected] wrote: > I don't see any reason why a company has to "last version for the OS/arch" > like FOREVER no exceptions. Keeping a simple build system around is > completely doable, even for a single-person op like yours.
Here's my single-person op perspective. I felt terrible dropping support for Snow Leopard, because it's a far superior OS to anything before it or anything that has come after it, but for me it came down to 2 things: 1. can I use the same source code for current and "legacy" compiling? 2. how does maintaining a "legacy" version affect my own quality of life? The answer to 2 is: it annoys me, and takes up my time. Usually the answer to 1 is simply "no", because of changes to the tools between versions, but sometimes it is "yes". I loved Real Studio and I really hated the Xojo IDE in comparison, but I've gotten "used to it", and it's all I use now. I use 3 versions of Xojo: (1) current version (Win 7+ and OS 10.7+) I use for all new projects, and this is what I work on 99% of the time (2) 2014r2.1 (last version to build Carbon applications) - I use this only for projects that still don't run correctly in Cocoa (3) 2013r3.3 (last version to support Snow Leopard) - I use this for projects that fit the needs of (2) and work when compiled with this tool, because - why not? I'm not a Windows user myself, only use it when I have to. I don't see any reason to support XP, since Microsoft dropped it, and Windows 7 is a much better OS as far as I can tell. I have an old Dell laptop that still runs XP and I haven't used it at all in the last 2 years. My Toshiba running Win 7 gets used whenever I compile and release updates, and I find that OS tolerable, bordering on pleasant sometimes :) Happy New Year everybody. Aaron _______________________________________________ Mbsplugins_monkeybreadsoftware.info mailing list [email protected] https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info
