The iPad 1 hasn't gotten an update since early 2012 with the release of iOS 5.1.1
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Here is why the iPhone 6/6 Plus didn't get more RAM.
- Thread starter Korican100
- Start date
- Sort by reaction score
The iPad 1 hasn't gotten an update since early 2012 with the release of iOS 5.1.1
Because Apple has no clue how to make a phone, and the Apple accountants dictate the amount of RAM.
So what does that have ANYTHING to do with what were talking about? We are saying more RAM allows these things, which is true, and that Apple purchasing in large quantities wouldn't pay much, which is true. Your point has absolutely nothing to do with any of that.
Your point appears to be that Apple decided the extra $10 wasn't worth it to there bottom line, which is great I guess. Its totally off topic.
THANK YOU.
It's like saying the engine of a Corvette puts out more horsepower than a Camry because the gas tank is bigger. The level of ignorance of some of these threads is absolutely astounding.
What I am saying is that Apple designed the iPhone to operate efficiently and I have more trust in them knowing how much RAM it needs than some guy at Tom's Hardware and a bunch of Internet parrots.
I'm saying that if it needed 2GB of RAM they would have put 2GB of RAM, cost be damned because they can easily charge for it.
I'm saying that these Internet jockeys second guessing Apple engineering with their constant whining about RAM is grating and annoying.
There. Clear enough for you?
HERE is why the iPhone 6/6+ didn't get more RAM.
What NONE of you obviously has is a working knowledge of how dynamic RAM allocation factors into this equation. The iPhone even at IOS 9 will never need any more than 1 GB of RAM because of the way dynamic ram allocation is built by Apple. This even comes into play with how many Safari pages are open.
All the models you're all talking about are RAM constructs and implementation within desktop computers not within iOS. Get yourselves educated please..
What NONE of you obviously has is a working knowledge of how dynamic RAM allocation factors into this equation. The iPhone even at IOS 9 will never need any more than 1 GB of RAM because of the way dynamic ram allocation is built by Apple. This even comes into play with how many Safari pages are open.
All the models you're all talking about are RAM constructs and implementation within desktop computers not within iOS. Get yourselves educated please..
So what your actually saying is you dont understand this, you admit you dont understand this, and youll just defer to Apple in all cases instead of listening to others criticize there decisions?
Thats fine. Why were you posting in this thread then?
And you are using the word sarcasm wrong btw.
----------
Dynamic Ram allocation? As in Heap based memory in the C language world?
Your above paragraph honestly doesn't make any sense at all.
So are we now saying that Apple KNOWS how to make a perfect phone and should not be second guessed?
Jebus...late to the 3g game, late to the LTE game, late to the NFC game, late to the screen size game, late to the front facing camera resolution game (facetime sucks on VGA res), late to the widgets game, late to the active notifications game.
I can keep going but unless people complain about these things, nothing will be improved!
Never settle especially for this kind of ******** pricetag!
Jebus...late to the 3g game, late to the LTE game, late to the NFC game, late to the screen size game, late to the front facing camera resolution game (facetime sucks on VGA res), late to the widgets game, late to the active notifications game.
I can keep going but unless people complain about these things, nothing will be improved!
Never settle especially for this kind of ******** pricetag!
I was correcting your inaccurate statement that the iPad 1 still gets updates. Nothing more.
I think the entire line of question "Apple KNOWS how to make a phone." is flawed. Its RAM. It doesn't take any large amount of knowledge or anything to understand the advantages of it. It doesn't take world class engineers to figure out how to properly use it. Its just pretty much always good to have more. Your limited by price and supply constraints. Clearly Apple decided these constraints were worth sticking with 1GB for longer, but its a shame.
This is not some futuristic request. People are talking about things as simple as switching back and forth between tabs in Safari (for example, while filling out a form). It happens all the time.
There are many phones out there with a lot more RAM than the iPhone. It's something Apple should have addressed in the 6.
HERE is why the iPhone 6/6+ didn't get more RAM.
If you were actually educated in DRA and mobile os architectures you'd understand why 1GB is plenty of ram for any mobile os. And how Samsung and other companies offering more is just a public pandering gimmick. Not based in any real lack in a 1GB mobile os architecture. Again.. Read up.. Knowledge is power and facts are inconvenient things sometimes.. aren't they..
I do know architecture. Very well actually. And any notion that iOS is built in such a way it cant use more RAM is nonsense (it actually just plain doesnt make sense).
Im assuming what your trying to say is that iOS is ram efficient, Apple manages their memory well, and there isnt a need for more RAM due to these optimizations they have in place. However I would argue (and many others would) that this is incorrect. To us, the ability to multi-task with third party applications is a very worthwhile want.
Lol okay well tell me why my Safari tabs constantly reload. It's not a feature, it's an annoyance.
That's all fine and dandy if you are just using it as a phone and basic web browser. In this day and age, websites are so media rich and games are so graphic intensive!
The OS may be ram frugal but the app usage isn't!
Hardware aside ---
iOS and Android OS (and windows mobile) optimize and utilize memory in different ways. Yes, more ram would help with the Safari tab reload issue but because Apple doesn't have TRUE multitasking (yet) it doesn't really matter that the RAM isn't as high as an operating system that does. Bottom line.
When iOS implements true multitasking, we will naturally see a bump in RAM on the iPhone. Until then, it isn't really necessary for the phone to function correctly.
So comparing an Android based phone's hardware specs to an iPhone's hardware specs is a little apples to oranges (or apples to random candy items?)
iOS and Android OS (and windows mobile) optimize and utilize memory in different ways. Yes, more ram would help with the Safari tab reload issue but because Apple doesn't have TRUE multitasking (yet) it doesn't really matter that the RAM isn't as high as an operating system that does. Bottom line.
When iOS implements true multitasking, we will naturally see a bump in RAM on the iPhone. Until then, it isn't really necessary for the phone to function correctly.
So comparing an Android based phone's hardware specs to an iPhone's hardware specs is a little apples to oranges (or apples to random candy items?)
I agree. The issue of apps reloading when switching to them is hardly a dealbreaker, which is why I still use iOS. It sure would be nice to have them instantly pop up though.
I feel like you have a very superficial, flawed understanding of this topic. You're using irrelevant benchmarks and logic.
The iPhone could do better with more RAM. Obviously it doesn't need it to carry out system processes and juggle a couple saved-state apps and games, but you can see it struggle with bigger loads.
The iPhone could do better with more RAM. Obviously it doesn't need it to carry out system processes and juggle a couple saved-state apps and games, but you can see it struggle with bigger loads.
Why can't I use Apple's browser on an Apple phone? I have used Chrome but I don't like it as much. Can't remember if the tab reloading is as bad, but if it's due to RAM shortage as I and many others suspect, I don't see why it would be any better.