I'm amazed there are always people like you, who will make a prediction about an operating system that won't be released for a year with no evidence to back it up (nothing in any of your posts supports your assertion that iOS 8 will have higher system requirements than 7 to such a degree that it won't run acceptably on this year's hardware). Fact about these people; nobody with half a brain listens to their FUD-spreading, nobody.
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.
iPad 1Gb of RAM is enough, be happy :)
- Thread starter MartinAppleGuy
- Start date
- Sort by reaction score
I'm amazed there are always people like you, who will make a prediction about an operating system that won't be released for a year with no evidence to back it up (nothing in any of your posts supports your assertion that iOS 8 will have higher system requirements than 7 to such a degree that it won't run acceptably on this year's hardware). Fact about these people; nobody with half a brain listens to their FUD-spreading, nobody.
A device that crashes with fours tabs now will NOT run well in the future. The iPad Air is ill fated from the start. Sorry about earlier; was being mean and was wrong of me.
No worries, I was a bit sharp myself.
I suppose it all depends if the issue with Safari is the system RAM or a memory leak bug, I guess we will know that in the next week or two when the next update comes out.
No worries, I was a bit sharp myself.
I suppose it all depends if the issue with Safari is the system RAM or a memory leak bug, I guess we will know that in the next week or two when the next update comes out.
Yip. I believe iOS 7.0.4 was getting worked on (I read it was seen in logs though...).
Most likely. The next iOS update whether its iOS 7.0.5 or 7.1 may address some issues, but 1GB versus 2GB is still a huge difference.
I just don't see especially the iPad with 1GB RAM being future-proof.
My sources are telling me that future generations of iPad's will only come with 512 MB of a ram and they will be so large and so expensive that only the five richest kings of Europe would own them.
Confirmed - it is breathtakingly bad. And if you dare use multiple apps you are likely to get reloads after just a couple of tabs.
With all of the intentional limitations and dumbing down, Apple is creating the WIndows CE devices for the 21st century ...
Try to compare Chrome for iPad and Safari on an iPad Air.
Try heavy sites with one tab and move gradually upward in the use of tabs.
The combination of 1GB and Safari's poor memory management turns out soon. I think that Apple can fix this issue wih some more by good optimization of code and error handling. But that cost money. Maybe iOS 8 is the way to go, rebuilding the memory management or something.
Try heavy sites with one tab and move gradually upward in the use of tabs.
The combination of 1GB and Safari's poor memory management turns out soon. I think that Apple can fix this issue wih some more by good optimization of code and error handling. But that cost money. Maybe iOS 8 is the way to go, rebuilding the memory management or something.
No worries, I was a bit sharp myself.
I suppose it all depends if the issue with Safari is the system RAM or a memory leak bug, I guess we will know that in the next week or two when the next update comes out.
Following these numerous memory shortage threads still has me wondering: if this is truly a RAM quantity issue then how in the hell do these graphically monstrous games, office apps, and everything else run so perfectly and smoothly? Are the developers of these apps THAT much smarter with memory management? Is safari and web browsing in general just a massive RAM hog?
I just don't get this... It doesn't make a lot of sense, IMO.
I haven't had any trouble with safari myself but I'm usually a couple tab user and that's it. Whatever though.
Yes, and yes. It comes back to years of optimizing for low-memory consoles, I think. Web browsing is hugely inefficient in terms of memory use. That is why a 2GB Chromebook turns into a slideshow after 4 or so tabs.
Hmmmm, so really what we are asking for is that web browsing stop being so damned inefficient and lazy as far as memory use is concerned? And, I suspect if memory management was proper then there wouldn't be any RAM threads?
Sounds to me like more RAM is just a band aid and better software is the REAL cure here. That's what I've been suspecting all along but we keep getting "more ram" threads nonetheless. Interesting.
Safari in need of heavy optimizing and updating, it's one of few web browsers in mobile that doesn't even have a true data saving mode.
At the moment on my iPad I do a maximum of 3tabs in Safari with A mix of the Facebook app and Twitter open, so 3tabs and 3 apps, and it seems to cope, but the moment I launch something else, when I come back to Safari Im faced with a tab reload, lol.
At the moment on my iPad I do a maximum of 3tabs in Safari with A mix of the Facebook app and Twitter open, so 3tabs and 3 apps, and it seems to cope, but the moment I launch something else, when I come back to Safari Im faced with a tab reload, lol.
It has been explained to you many times in numerous threads. I've posted videos of two tab reloads in saari with nothing else running. Having amazing third party games/apps staying within their RAM allotment has been explained many times.
Great games/apps can be made while using less than 500Megs of RAM. Why is that hard to understand?
Many are experiencing issues while doing very little. Can imagine what a joke the air will be when multitasking comes in ios8? It's barely passable now for folks who use safari.
And you wonder why there is complaining?
----------
lol - check out my video on the other thread - 1 app(safari), 2 tabs, and I get reloads. 3 and 3 would be amazing!!!
What's hard to understand is that a game like real racing, hearthstone, and plenty of others with thick graphics, sprawling stories, and features run on such little RAM yet a freegin browser pukes after a few tabs. It's been noted that safari and it's java engine are pigs so it makes sense to me that those items might be worth looking at.
Just throwing hardware at a software problem is a quick fix but adds costs and possible complexities. Then, when the Air gets 2GB of RAM and still has reloads or whatever else after a few more tabs are opened....then what? I know, the Air now needs 4GB or RAM. Then.... After that.... You know where this is going.
Nothing tangible has been explained to me at all. There is very little common sense in any of this. Some of us see the reloads, some don't. Super high end games somehow magically run on one byte of RAM but a web browser cannot.
Don't make it like this is a simple, cut and dry issue. It's not even close to that.
Amazing programs can be architected and implements to run within the guidelines put forth by Apple for 3rd party apps. They have a GREAT incentive to do such - the better they are, the more will be downloaded, and the more money will be made. Safari is made by employees. Their incentive is to produce code within the schedule of the project. They have less incentive to try something revolutionary to make webkit more efficient because of the APIs, interfaces, dependencies, etc... that are impacted by such a move. There are orders of magnitude more implications/complexities involved in making webkit more efficient, than in creating a standalone game. It really is that simple.
That is how you get revolutionary games/apps(stand alone) versus revolutionary iOS infrastructure software.
It is that cut and dry.
I think you are confusing visual complexity with programming complexity. Just because something is visually complex, doesn't necessarily mean that it takes up system resources. A webpage may look simple, but especially with how many ads are on a typical webpage these days, a single webpage with 2-3 ads, some pictures, lots of text, response boxes, etc, might take up more system memory than a few seconds of high intensity video.