Exactly. That's basically what I told them. I use a galaxy s3 and it's plenty big to do what they want me to do. It's absolutely ridiculous my work would buy iPads for everyone when most of us (seeing a lot of my coworkers use Galaxy devices) don't need them.
My Rant on the iPhone 5s
- Thread starter DroidArmy
- Start date
- Status
Exactly. That's basically what I told them. I use a galaxy s3 and it's plenty big to do what they want me to do. It's absolutely ridiculous my work would buy iPads for everyone when most of us (seeing a lot of my coworkers use Galaxy devices) don't need them.
So now, instead of having apps that scale up badly on iOS, you can't even use those apps? So that means that you have about 1 million apps available on Android tablets, maybe 100,000 of which are optimized for tablets, and the rest of which aren't optimized but still work well on tablets, and while all apps for the iPad are optimized, there are only 400,000 available to download? I don't think that's a good solution.
Last edited:
What? Apple by default shows iPad apps but you can choose to use iPhone apps.
Posted via Android Central App
How many times do I have to specify I'm talking about apps that actually USE the extra capability that 64 bit can give? Not just the same old app with the same old functions just simply converted to 64 bit? I think this is the 3rd time I've made that clear. Do you need a few more? Do I need to break out Google translator or something? How is this hard to grasp?
Any app that uses encryption or decryption will enjoy the benefit of 64 bit and probably be faster in some regards.
The problem is, you may never noticed it or never knew that was the case.
JHBThree
Well-known member
- Feb 15, 2012
- 4,096
- 147
- 0
You're confused. You don't have to add anything to take advantage, because xcode does that for you, exactly as he described.
Sent from my Nexus 4 using Tapatalk 2
Please stop giving Chetan "I love my veggies" Takyar credit for repeating my postings. It will go to his head.
Perhaps you explained that in another thread. Perhaps one I am not participating in.
Posted via Android Central App
Tell me what the difference is between these two:
Scenario one: an app converts from 32 to 64 bit app, otherwise nothing about how it works is changed.
Scenario two: developer decides they want to add a bunch of complex capabilities not possible until now because 32bit wasn't capable of allowing it.
Can you explain what exactly is automated about scenario two?
Chet was trying to convince me that it's only going to take 3 months MAX for the majority of the devs in a store of nearly a million apps to not only do this, but to be motivated to do so. That right there is the part I find ludicrous, nothing more, nothing less.
Nothing in the code about complex calculations, only code that really needs to change is assembly language. Data size and alignment is different so you need to take into account if you are exchanging app data between the 32bit version and 64bit version of the same app.
I can go into examples of this if you like.
Not required, that was never the point of disagreement, I already stated my disagreement is with the timing.
He is probably saying that all the apps will be 64 bit because of the dual binary when updated. When it comes to data types, that automatically changes with going to 64 bit, so some items will be planned carefully. I have no clue on a timeline myself but I would be worried about any app that uses iCloud to sync data.
what Apple did was move their custom ARM-based system-on-a-chip processors to 64-bits so that someday you could have iPads and iPhones with a lot more memory in them
That day isn?t today. The iPhone 5S still has 1GB of memory (not storage, memory, the place where programs run) and you only need 64-bit chips when you want to go past 4GB of memory. And it?s important to note that most programs (almost 100% of them?!) will continue to be written in 32-bit code to support the 95+% of iPhones that won?t have the new A7 chip but will support the developer?s apps.
So that leaves Apple able to run mostly its own code faster and better on the new chip and some developers able to also take advantage. This is a good thing, but for Twitter and Facebook FB and Gmail, you are not likely going to notice. In fact, those apps could all benefit more from code optimization than from trying to brute force better performance on the processor side. And by moving to more bits rather than just a faster clock speed, that brute forcing is unlikely to feel like a detectable improvement anyway.
That day isn?t today. The iPhone 5S still has 1GB of memory (not storage, memory, the place where programs run) and you only need 64-bit chips when you want to go past 4GB of memory. And it?s important to note that most programs (almost 100% of them?!) will continue to be written in 32-bit code to support the 95+% of iPhones that won?t have the new A7 chip but will support the developer?s apps.
So that leaves Apple able to run mostly its own code faster and better on the new chip and some developers able to also take advantage. This is a good thing, but for Twitter and Facebook FB and Gmail, you are not likely going to notice. In fact, those apps could all benefit more from code optimization than from trying to brute force better performance on the processor side. And by moving to more bits rather than just a faster clock speed, that brute forcing is unlikely to feel like a detectable improvement anyway.
- Status
Similar threads
- Question
Trending Posts
-
Google wallet not working after latest update
- Started by AJ69
- Replies: 21
-
-
-
OneUI 8 beta coming week of August 11, 2025- Started by Laura Knotek
- Replies: 0
-
Facebook
Twitter
Instagram