And a different discussion from the messaging one. Not to mention that that's not what they seem to want and not how they really go about moving things ahead based on their plans.Preventing it would be even better.
And a different discussion from the messaging one. Not to mention that that's not what they seem to want and not how they really go about moving things ahead based on their plans.Preventing it would be even better.
It's all linked, not a different discussion, unless you're here to guide a discussion in a specific direction. Really poor user experience in iOS this is. Fingers crossed this rubbish doesn't make it past the beta. Good day.And a different discussion from the messaging one. Not to mention that that's not what they seem to want and not how they really go about moving things ahead based on their plans.
An excellent port of original DOOM by idsoftware the original makers. The first Infinity Blade game (I have all three). Otherwise I am all for updating to 64 bit...Which games....?
If it's happening then the messaging is better than no messaging. Whether or not it should be happening is separate from that. Going in circles won't change any of that.It's all linked, not a different discussion, unless you're here to guide a discussion in a specific direction. Really poor user experience in iOS this is. Fingers crossed this rubbish doesn't make it past the beta. Good day.
I bought an app that is not even on the app store anymore. Nevertheless it does what it is supposed to do and I don't care when it's not touched by the developer for the next 10 years if it was done properly when it came out. On the contrary, I really dislike very frequent app updates and constant changes no one asked for.Apple has required all submissions, including updates, to be 64-bit compatible for the past 2 years. So at minimum this means that the developer hasn't touched the app at all in 2 years. So it is probably not commercially viable. And the only reason Windows supports 32-bit applications as much as it does is that Microsoft botched the 64-bit rollout (they still default to 32-bit Office in Windows).
To each their own there. Many people like when developers push out updates to fix bugs and heed users' feedback in terms of changes. Besides, Apple even introduced automatic app updates so that people do not have to keep checking the app store to reduce this friction. You are free not to update if none of this does not sit right with you.On the contrary, I really dislike very frequent app updates and constant changes no one asked for.
How about developers actually testing their apps before releasing them... both for bugs and for features that the users would actually want? I see you prefer being a test rabbit helping to debug products you payed for, assuming they actually work flawlessly.To each their own there. Many people like when developers push out updates to fix bugs and heed users' feedback in terms of changes.
Yes, what a great idea, especially in combination with changing the app to the degree when the new version cannot do what the old version could and there is no way to revert to the old version.Besides, Apple even introduced automatic app updates so that people do not have to keep checking the app store to reduce this friction. You are free not to update if none of this does not sit right with you.
Looking forward to seeing millions of 32-bit apps disappear from the store because the developers don't see it as worth the cost to update
Apple could just continue to put up their current message that indicates the 32-bit app may affect performance. To cut off those apps altogether is unnecessary.
And Apple could also still support floppy disks and cd drives.
You are "swimming upstream" on this one I'm afraid. Most Apple customers are accepting of "disposable" these days, disposable hardware (that is glued and soldered into a single unit) so it makes sense that seeing software become disposable would be good to them as well. #shrugHow about developers actually testing their apps before releasing them... both for bugs and for features that the users would actually want? I see you prefer being a test rabbit helping to debug products you payed for, assuming they actually work flawlessly.
Yes, what a great idea, especially in combination with changing the app to the degree when the new version cannot do what the old version could and there is no way to revert to the old version.
Thre is such a thing Apple "could do" and it would affect so many users, but how many people today depend on floppy drives ?
Nah, it's a completely awkward way to do it. Hate bringing Steve Jobs in to this, but he would have said this is a rubbish way to do this. This is completely the windows way to do things.
Not "putting words into the mouth of a dead person", it's an observation based on the past explanations and behaviors from that person while they were alive.I see you're still just repeating yourself, but now also resorting to putting words into the mouth of a dead person. I suppose there's some logic to calling on someone who has gone over to the other side to get help in beating an (also) dead horse.
Not "putting words into the mouth of a dead person", it's an observation based on the past explanations and behaviors from that person while they were alive.
You've taken my comment to the extreme and blown it out of proportion. Based on SPJ patterns of work, Windows-like prompts with a single "OK" button would have been culled at the first alpha. The fact this stuff is making it into beta and final iOS releases is astonishing. It's ugly thoughtless design that gets the user thinking about maintaining their device.Steve Jobs is dead. I can say with 100% certainty that he currently has no opinion on this matter. To say that he does is to use his name without his permission in order to support your opinion about something. Colloquially, that's described as "putting words in the mouth of a dead person."
If you can show evidence that the man had an opinion against using an OS prompt to warn users about legacy software being phased out, I'll gladly concede my point. If all you've got is your impressions about what he thought about some other things and those lead you to believe he would feel a certain way about this issue, that's still your opinion, not the dead guy's opinion, and you should let it go. It's already abundantly clear to anyone reading this thread what your opinion is already.
It's an optional feature and has been an opt-in since it was introduced. Many apps rely on back-end stuff from other providers working properly. In an event that it does not, devs have to rush updates to patch issues and, for users, it presents a seamless experience. You don't have to like it, you don't have to enable it, but venting your anger is best directed at app developers who it seems did you wrong as opposed to this forum.Yes, what a great idea, especially in combination with changing the app to the degree when the new version cannot do what the old version could and there is no way to revert to the old version.
Warnings about something that is coming up are better than something happening without any warning.You've taken my comment to the extreme and blown it out of proportion. Based on SPJ patterns of work, Windows-like prompts with a single "OK" button would have been culled at the first alpha. The fact this stuff is making it into beta and final iOS releases is astonishing. It's ugly thoughtless design that gets the user thinking about maintaining their device.
You've taken my comment to the extreme and blown it out of proportion. Based on SPJ patterns of work, Windows-like prompts with a single "OK" button would have been culled at the first alpha. The fact this stuff is making it into beta and final iOS releases is astonishing. It's ugly thoughtless design that gets the user thinking about maintaining their device.
I am not venting my anger... I do not and never will rely on iPhone/iPad to do anything critical because of Apple's loosing their mind. I am merely making the observation that the direction the Apple ecosystem is going is badly broken, IMHO.It's an optional feature and has been an opt-in since it was introduced. Many apps rely on back-end stuff from other providers working properly. In an event that it does not, devs have to rush updates to patch issues and, for users, it presents a seamless experience. You don't have to like it, you don't have to enable it, but venting your anger is best directed at app developers who it seems did you wrong as opposed to this forum.
The screenshot I shared is of Xcode, the primary IDE for iOS development. Others exist, but the LLVM compiler likely handles it pretty well in those, too, and they tend to be more costly than Xcode's price of $0.00. As long as an app doesn't get into any low-level shenanigans, which I'm not sure is even allowed in iOS (the need certainly hasn't arisen in the development of my first app), it really is that easy.Most apps? Have you surveyed developers to draw that conclusion or are you just making that up?
If the app submits Bitcode to the App Store along with the app itself, yes (kind of). This is intermediary code which allows the app to be recompiled automatically by Apple as new technologies/requirements arise, without surrendering the actual source code to Apple.On topic: Do Apple have the source code for the apps that are submitted to the store? Could they not re-compile it to ensure there is a 64-bit binary?
Agreed on this and your prior related points. This reminds me of programs that display ( for example ) warning messages when a button is clicked indicating that an option isn't available. The right design would be to disable the button( in whatever scenario makes that button click wrong ) so the user can't select it thus avoiding the error message. ( i.e. you don't allow the user to choose an unavailable option )The warnings shouldn't be there. Apple, just make it work. It just works. That's what's it's meant to do. The two prompts are stupid as bad operating system software gets. Certainly not elegant.
Look, I accept that you have had some undesired experiences in the past. I think that we have all been bitten by such from time time. On the other hand, you should accept that iOS and its ecosystem of devices is not for everyone.I am not venting my anger... I do not and never will rely on iPhone/iPad to do anything critical because of Apple's loosing their mind. I am merely making the observation that the direction the Apple ecosystem is going is badly broken, IMHO.
Yes, you/I can opt out... but my 80-years-old (who is otherwise perfectly OK operating computers but has no time/desire to learn all the small ever-changing Apple quirks) gets a "little bit" upset when his iPhone installs an OS update in the moment he needs it least, just because iOS bugs him EVERY DAY to do so and he happens to unintentionally tap the wrong button once. And guess what, the next thing, the shiny new iOS iteration starts app auto updates without asking! What a feature: say the update starts while you are on a wifi but does not complete. Then you move to mobile data -- the update stops and you are either f****ed with a broken app or you are forced to consume your mobile data to finish the update.
It's one of those "smart" automations which actually only stand in people's way instead of helping in any substantial way. Apple should concentrate on implementing reasonable things instead -- like sms delivery confirmation (without writing a network-specific string at the beginning of each message)... a functionality that ALL OTHER phones have since the very beginning of GSM. But no, we have emoji, apps in messages, autoupdates and similar non-sense instead...
Isn't this in the beta though? Nobody knows if it will be carried through to the final release. I haven't hit the message myself, though.
[doublepost=1486012003][/doublepost]
Okay, I haven't hit the message myself, but I don't really see it as a bad thing. And as I just said, this may disappear anyway for the final release.