In other words, most of the abandonware was made in the two years leading up to the 64-bit requirement despite ample warnings. Instead, we saw that most developers didn’t bother, and by the time 2015 rolled around, and 64-bit became mandatory, many had still published 32-bit apps in the two preceding years. That was the point developers should have made the transition. Not long after, 64-bit was set to default for new projects in Xcode. The transition to 64-bit started in 2013 with iOS 7, 5 years after the App Store launched and included a 64-bit compiler in Xcode 5 that year. You’re acting like this is about decades-old software with obscure source code that’s nowhere to be found. It’s grafted together from all kinds of components that originate from pretty much every Windows in existence. You see them attempting this with their abomination, that is, the control panel and its underlying systems. It’s simply not feasible to ensure compatibility in perpetuity and deliver a smooth, innovative experience. While annoying, I can’t fault them for it. NET frameworks, track down obscure dlls, or generally run into compatibility issues. > Microsoft's MO has been that once the end user has acquired an executable, that program will keep working damn nearly forever. So, we weren’t exactly in the stone ages of software development. At the start of the transition, more than half of the developers were using Git, and another 40% were using SVN. > (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!) 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. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |