Earlier quoted context omitted.
If they got depreciated once, it's gonna happen again. Apple should invest in Microsoft-tier backwards compatibility if they want to avoid publishers abandoning their software.
I suspect Apple considers developers ignoring a five(?) year notice period that 32 bit compatibility will be dropped a sign that the publisher has already abandoned their software.
ScummVM on the App Store
141–150 of 197 posts
Re: ScummVM on the App Store
#142Earlier quoted context omitted.
That was never Apple's thing. Apple always changes things as it pleases and expects the developers to suck it up. https://www.youtube.com/watch?v=oeqPrUmVz-o
Not sure if you linked the wrong video, but the one you linked to barely supports your comment. Setting aside that abandoning OpenDoc turned out to be the right call, I see a dude trying to get a rise out of Jobs and Jobs handling it in a very respectful way, going as far as admitting they make mistakes and that he is flawed, but that ultimately the decisions are made with the end user (and sales) in mind and less wi…
How are teams that no longer exist supposed to recompile anything? Plenty of source is laying around where the last person who knew how to compile it left the company years ago and no one even knows how to check the software out from the source repo anymore.
(Pre Git, it wasn't always obvious how to even pull software down from repos, tools like perforce allow for fancy remapping of folders so you cannot necessarily just pull source down, also I've worked in repos where you needed specially modified scripts that weren't in the repo so you could actually build things!)
Microsoft's MO has been that once the end user has acquired an executable, that program will keep working damn nearly forever.
16bit support was the only time they ever dropped anything, and people are still upset about that.
Re: ScummVM on the App Store
#143Earlier quoted context omitted.
Happy to sign all the necessary NDAs and to port them to 64 bit, newer iOS versions and devices for free.
If they got depreciated once, it's gonna happen again. Apple should invest in Microsoft-tier backwards compatibility if they want to avoid publishers abandoning their software.
As an end user it’s already annoying how, mainly big devs, are extremely slow in adopting the latest APIs, this would only motivate them more to just sit on their laurels.
As a dev for Apple platforms it would become a buggy mess and would lead to less bumping of target OS versions, which in turn leads to needing to reinvent wheels and coming up with time consuming workarounds.
Just one look at the gazillion ways Windows 11 has implemented configuration apps, from as far back as the XP era, has me shudder. You start out with Win 11 stuff but oh, you want to use that one thing? Now you’re lopped into Windows 7 stuff oh you want this other thing, enjoy this XP app, etc, etc. All in the name of backwards compatibility, no thank you.
Hell, the fact that they had to skip Windows 9 because of so many devs checking for a 9 to detect 95/98 is another such messy nonsense.
If I had to choose between that experience or Apple forcing me every year to learn an entirely new programming language + UI framework + persistent storage framework I’ll happily become a polyglot because the MS way of doing things is ridiculous.
Re: ScummVM on the App Store
#144Earlier quoted context omitted.
That was never Apple's thing. Apple always changes things as it pleases and expects the developers to suck it up. https://www.youtube.com/watch?v=oeqPrUmVz-o
Not sure if you linked the wrong video, but the one you linked to barely supports your comment. Setting aside that abandoning OpenDoc turned out to be the right call, I see a dude trying to get a rise out of Jobs and Jobs handling it in a very respectful way, going as far as admitting they make mistakes and that he is flawed, but that ultimately the decisions are made with the end user (and sales) in mind and less wi…
This assumes you have all the source code for everything available, the person to do it ready, and that no compiler errors anywhere have crept in through the many revisions of the SDK. None of these assumptions hold for iOS ports that sold poorly (as most did), that were done by some team (likely defunct) as a one-off, that probably used a bunch of middleware they didn't own. It's just not worth it, otherwise it would've happened.
Re: ScummVM on the App Store
#145Earlier quoted context omitted.
If they got depreciated once, it's gonna happen again. Apple should invest in Microsoft-tier backwards compatibility if they want to avoid publishers abandoning their software.
God no. As an end user it’s already annoying how, mainly big devs, are extremely slow in adopting the latest APIs, this would only motivate them more to just sit on their laurels. As a dev for Apple platforms it would become a buggy mess and would lead to less bumping of target OS versions, which in turn leads to needing to reinvent wheels and coming up with time consuming workarounds. Just one look at the gazillion…
Re: ScummVM on the App Store
#146Earlier quoted context omitted.
iSH has compiled the binaries for arm64 so they actually run natively. When they do a syscall to malloc they are actually doing a syscall to malloc. iDOS is interpreting the bytecode and wrapping the unavailable things with its own implementation. When a DOS application runs malloc, the memory is assigned by iDOS instead. I’m not saying Apple is consistent, but your example doesn’t show that well.
Isn't iSH literally an x86 emulator?
Re: ScummVM on the App Store
#147Earlier quoted context omitted.
If they got depreciated once, it's gonna happen again. Apple should invest in Microsoft-tier backwards compatibility if they want to avoid publishers abandoning their software.
God no. As an end user it’s already annoying how, mainly big devs, are extremely slow in adopting the latest APIs, this would only motivate them more to just sit on their laurels. As a dev for Apple platforms it would become a buggy mess and would lead to less bumping of target OS versions, which in turn leads to needing to reinvent wheels and coming up with time consuming workarounds. Just one look at the gazillion…
Re: ScummVM on the App Store
#148There is also Dreamm https://aarongiles.com/dreamm/
DREAMM is a pretty significant project, and differs from ScummVM in a few ways. Primarily, ScummVM is an engine rewrite. They write new code that copies the behaviour of the original games. Aaron Giles worked at LucasArts and was instrumental in porting SCUMM to Windows (for Full Throttle and Curse of Monkey Island). DREAMM is a full x86 emulator that takes the original game code and runs it directly.[0] Amusingly en…
On the other hand it only does LucasArts games so you need both DREAMM and ScummVM.
Re: ScummVM on the App Store
#149Earlier quoted context omitted.
I suspect Apple considers developers ignoring a five(?) year notice period that 32 bit compatibility will be dropped a sign that the publisher has already abandoned their software.
A "notice" doesn't pay bills. If the cost of porting over is expected to exceed future revenue, the publisher can not be expected to foot the bill.
Re: ScummVM on the App Store
#150This reminded me of the fact that excellent remasters of monkey island were released on the iPhone (and a few other paltforms) but were removed from the App Store after a few years. It’s a shame, they had great new artwork and sound/music but you could switch back and forth with the old art and it was cool to see the difference in each scene.
I was so pissed when I went to re-download them and they disappeared even from my Purchased list. Complained to Apple and they basically said "shouda made backups, good bye and fuck off". $12 down the drain.