Where to draw the line is the difficult one but not modernising at a fast enough rate to attract new users and keep cutting edge users on board has to be a factor. I do agree with Mike that a sensible policy with regard to backward compatibility should be maintained. I will not give up on SC, as it is, in my opinion, better than LiveCode for Mac users (renting software is not for me), it’s just a shame it has taken so long to bite the modernise bullet. I assume removing the text engine and incorporating Cocoa is quite an exercise. The time consuming stumbling block would appear to be WASTE. The performance of 4.8 when compared to 4.73 does appear inferior and this may be because of a mixture of Cocoa/Carbon code as Mark migrates areas of SC. I know Mark has been hard at work to get 4.8 to this state but for me there is insufficient to warrant my investing in the upgrade at the moment. I am not interested in running SC in a virtual machine as 4.8 is slow enough. I did go back to Sierra after initial disappointment but have now settled on High Sierra (still prefer Sierra). I only have one computer and that is running High Sierra. I am waiting to see the lay of the land/timing from Apples perspective with regard to the dumping of 32bit before I consider upgrading SC. I for one would have preferred to go from 4.73 directly to 5(Cocoa/64bit?). If Mark were free of most, if not all, of the shackles of backward compatibility, would updates happen at a faster pace? Would we be further along in the migration to Cocoa SuperCard? Would we be at 64-bit support already? Would Mark be able to use the latest version of Xcode to take advantage of anything that Apple has put there to make things easier for developers? Don't get me wrong, that range of support is extremely impressive and a true testament to Mark's incredible skills, but I have to ask where we might be today if that length of backward compatibility was maybe shortened a bit. One has to wonder how many hours, days, weeks, or months Mark might have spent fixing something to maintain that support for older versions, or conversely, how many hours, days, weeks, or months Mark had to toil over the code in order to resolve issues with something newer ONLY because easier and faster fixes would have required dropping some of that older support. I am a bit concerned about the impact of maintaining such compatibility over such a large number of macOS upgrades though. Thank you for all of your time and effort into this 4.8 release! If you do plan on charging for it, I completely understand, it’s just something I would want to know before I pay for this current version. So, to be clear, if we intend on updating to macOS 10.14 around September, then this version of SuperCard will not launch, and it would only be useful for about five months? And in that case, will the 64-bit version be a free update? I’m only asking because I’m not sure how many people will want to pay again for an app that will only work for them for five months. So it'll be done when it's done, and I've had far too much bitter experience already with both Carbon AND Cocoa to promise more than that. But I'm not, so I'll just tell you the truth: I believe it's doable and I'm working on it, but between here and that land of milk and honey thar be dragons. If I were a salesman I would tell you what you obviously want to hear (i.e., that there will definitely be a 64-bit Cocoa version of SuperCard available before Apple pulls the plug on Carbon).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |