That's pretty clever if they figured out how to do that with the Atomic browser. Do you have any kind of source on that?
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.
Is The Lack Of Ram Annoying Now?
- Thread starter Konvictz
- Start date
- Sort by reaction score
That's pretty clever if they figured out how to do that with the Atomic browser. Do you have any kind of source on that?
http://apple.stackexchange.com/a/56165
I'm not an iOS developer, but unless Apple has removed the APIs for this (which I doubt), I'd wager it's in the development docs somewhere. But intrinsically, it is akin to an app using flash memory for storage. I suppose Apple must have made some design choices to preclude Safari from doing the same (perhaps they felt Reading List is sufficient).
Dude, seriously. You are either drunk or just confusing me with someone else. What 2GB trolling from ME are you talking about????
Both components will determine the speed of your device. The CPU will control how quick information is processed by the device, and the amount of RAM controls the multitasking ability of the device. In general the faster the processor and the greater capacity of RAM determines both the processing and multitasking capability of the device.
I would be very happy if they allowed the option to have safari create a swap partition. I would gladly give up 2 gbs or more of storage for it.
There is nothing stopping any app to write their settings/content to disk. There are several states in the framework that you can invoke and have a varying level of saving caching which ever you want to refer to it for data. Just like where to reload it from when the focus comes back. That really isn't an issue.
If I could be bothered I would write it. To me it just isn't an issue and not worth my time to do that. Much more interesting and profitable projects to work on.
If I could be bothered I would write it. To me it just isn't an issue and not worth my time to do that. Much more interesting and profitable projects to work on.
Now that it is confirmed that the iPhone 6/6+ has 1 GB RAM, how do you feel about it? Are you disappointed that Apple didn't include 2 GB?We're not even sure until release and reviews are out how much RAM exactly either device will have.
If it can be fixed with software, why the heck has this issue been present for years on iOS devices, and why is it getting worse with each new version of iOS?
I think 2gb should be coming next year. At the moment iPhone 4s/ipad 2 and mini are still around with 512mb, the iPhone 4s should be gone with ios 9 and I'd expect ipad 2 to go and maybe even the mini too. That at least would mean 'supported' devices would have 1gb min and 2gb max. I'd be surprised if the new iPads this year don't have 2gb, but then maybe not if they prefer to have all the A8 chips relatively the same.
I also see 'true' multi-tasking as the next 'big feature' soon - it just makes sense with the larger iPhones coming out to be able to have more on the screen at once. The code for split screen was already found in ios 8 betas iirc. And then of course there are all these rumors of an 'ipad pro' that would also benefit from more than one app open at once.
I also see 'true' multi-tasking as the next 'big feature' soon - it just makes sense with the larger iPhones coming out to be able to have more on the screen at once. The code for split screen was already found in ios 8 betas iirc. And then of course there are all these rumors of an 'ipad pro' that would also benefit from more than one app open at once.
The only thing annoying is these threads. No, I'm not annoyed that I can literally open every single app on my phone and it will perform exactly the same as if nothing was opened.
Just thought I'd throw my hat in the ring here because, well why not, I'm bored lol.
Being a naturally curious person and because I really needed a wee break from the app I'm working on. I thought I'd see just what might be possible with the 1GB of memory that for a lot of people gives the impression of not being enough.
Now I'm not saying there aren't issues with things like Safari reloading, of course there are, we've all seen it. All I wondered was if there was a good reason for it, or if perhaps as has been suggested it's just not worth the hassle of fixing for the sake of a couple of seconds reloading time.
So for the past couple of days I've been tinkering away making a web browser, of sorts, just to see how far I could push it.
I'm using my new iPhone 6+ for the testing as it's the latest device and therefore theoretically the most capable.
Now a couple of caveats before I put my findings. First of all, I'm not the greatest of coders, not by a very long shot. Anyone who uses my apps would probably say mediocre at the best of times
Secondly, when I say web browser I mean a basic testbed. Very, very basic. There's no luxuries like forward and back navigation. No bookmarks, no sharing features, no pretty design, no nothing.
It loads websites and it does tabs. That's it, nothing else, it doesn't even persist data. So if your phone goes into standby or you close the app (and I use the term loosely) everything is gone.
Basically it's bloody basic is all I'm saying
Anyhooo, that rather long winded (it's my morphine......again, sorry) introduction is probably a fair bit of overkill for this short test result.
I can get 14 tabs at a push open and fully loaded, full desktop versions where possible, with absolutely no reloading when switching between them.
May even be possible to get a lot more if it were a decent coder that knew what they were doing better.
After that the app, sorry test thing, just unceremoniously craps out back to the home screen.
The monitoring tool reported memory usage at just under 400MB at it's peak before it all went south.
So if a largely useless lump such as meself can do that, Im reasonably happy in saying that the measly 1GB of memory is probably enough to be getting on with for now.
Now I know, what your thinking. That doesnt stop my Safari from refreshing all the time or this that and the whatever next thing not doing what you want it to.
And your dead right, but I think it shows in some small way that the hardware in that tiny little box of wonders your holding in your hand can be very capable for the time being.
There will be many contributing factors as to why various apps perform the way they do, all Im saying is that after my tests Im less likely to blame the hardware.
I think my wee test goes some way to showing that with the right combination of hardware, operating system and dedicated geniuses that work at Apple a lot can be done with very little.
Now as my missus will be home with my dinner very soon and as after all that I'll have bored the nipples right off ye, i'll shut up and bring this unwieldy post to a long overdue end
Being a naturally curious person and because I really needed a wee break from the app I'm working on. I thought I'd see just what might be possible with the 1GB of memory that for a lot of people gives the impression of not being enough.
Now I'm not saying there aren't issues with things like Safari reloading, of course there are, we've all seen it. All I wondered was if there was a good reason for it, or if perhaps as has been suggested it's just not worth the hassle of fixing for the sake of a couple of seconds reloading time.
So for the past couple of days I've been tinkering away making a web browser, of sorts, just to see how far I could push it.
I'm using my new iPhone 6+ for the testing as it's the latest device and therefore theoretically the most capable.
Now a couple of caveats before I put my findings. First of all, I'm not the greatest of coders, not by a very long shot. Anyone who uses my apps would probably say mediocre at the best of times
Secondly, when I say web browser I mean a basic testbed. Very, very basic. There's no luxuries like forward and back navigation. No bookmarks, no sharing features, no pretty design, no nothing.
It loads websites and it does tabs. That's it, nothing else, it doesn't even persist data. So if your phone goes into standby or you close the app (and I use the term loosely) everything is gone.
Basically it's bloody basic is all I'm saying
Anyhooo, that rather long winded (it's my morphine......again, sorry) introduction is probably a fair bit of overkill for this short test result.
I can get 14 tabs at a push open and fully loaded, full desktop versions where possible, with absolutely no reloading when switching between them.
May even be possible to get a lot more if it were a decent coder that knew what they were doing better.
After that the app, sorry test thing, just unceremoniously craps out back to the home screen.
The monitoring tool reported memory usage at just under 400MB at it's peak before it all went south.
So if a largely useless lump such as meself can do that, Im reasonably happy in saying that the measly 1GB of memory is probably enough to be getting on with for now.
Now I know, what your thinking. That doesnt stop my Safari from refreshing all the time or this that and the whatever next thing not doing what you want it to.
And your dead right, but I think it shows in some small way that the hardware in that tiny little box of wonders your holding in your hand can be very capable for the time being.
There will be many contributing factors as to why various apps perform the way they do, all Im saying is that after my tests Im less likely to blame the hardware.
I think my wee test goes some way to showing that with the right combination of hardware, operating system and dedicated geniuses that work at Apple a lot can be done with very little.
Now as my missus will be home with my dinner very soon and as after all that I'll have bored the nipples right off ye, i'll shut up and bring this unwieldy post to a long overdue end