![]() ![]() So, the notion that there were no people around or that the source code was inaccessible is not believable. Most of the abandoned apps and games were created in the two years between the start of the transition and the deadline, not to mention that many of those developers happily published other apps and games after the transition was complete. This transition started five years after the birth of the App Store. > 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. ![]() In fact that’s what most indie devs love about it.Īs I stated in a reply to a similar comment below, the way you’re framing it doesn’t reflect the reality of this specific 64-bit transition. So I have no lost love for devs that couldn’t be arsed, even ignoring the fact that the entire ecosystem is known for rapid improvements and continuous maintenance. Specifically on the matter of 32-bit support, not dropping it would’ve meant not being able to make the leaps forward that they were able to make, which led to a better user experience.įrom the developer side of things, as a developer for Apple platforms, it’s a silly discussion to begin with because in 99% of the cases it just meant recompiling it against the latest SDK. 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 with what kind of nifty technology is behind it. Not sure if you linked the wrong video, but the one you linked to barely supports your comment. 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. 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. 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.Īll in the name of backwards compatibility, no thank you. Just one look at the gazillion ways Windows 11 has implemented configuration apps, from as far back as the XP era, has me shudder. There are a large number of fixes in the soon to be released 0.11.0 version (I should have another test release out today if I get time) but I doubt there will be much benefit for COMI in the release.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.Īs 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. The focus for the GP2X port is not to get COMI working but rather to optimise and bug fix other games for the GP2X 1st (the ones that run at or near to 100% of full speed). It is also not a game I regularly test (well I can’t test anything at the moment as I have no GP2X but that is not the point ) I am always looking at ways to speed up games and the port in general so COMI performance will improve but it is never going to run at full speed on the GP2X. If you’re desperate to try, the version used to complete COMI was 0.9.1. ![]() not worth the effort).ĬOMI is apparently fully completeable on the GP2X (yes, people have been daft enough to play it all the way through) but I can’t see how it would be a very pleasant experience. Cleaning up each frame would leave the game running at about 8% of full speed (i.e. As you mention it is quite unpleasant to look at but it is the only real option I have to maintain the 40-50% of full speed. The code I use to fit the graphics on the screen is crude at best (in simple terms every other pixel is removed to make the screen 'fit'). (Use the 0.10.0 list over the current SVN list as a lot has changed in current SVN of late).įor note: the COMI.LA2 is on the 2nd CD, I have just checked my various versions and it is there on all of them.Īs you can tell from the compatibility list, COMI is unlikely to ever be fully supported on the GP2X due to the high graphical and processing requirements of the game. The GP2X port/backend in common with all the other non-PC ports has its own compatibility list that is supplemental to the main one. What compatibility list are you looking at?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |