Doubling RAM On Smartphones Is "Silly"

Is Disposed a puppet account of CreepyUncleGoogle?

You mean besides the fact that i have been here twice as long and we agree on nothing? How the fuck do you even make that stupid ass connection?
 

Indeed. You don't need insane amounts of RAM. Frame rates and loading times were the same. AMD 9950BE, GTX 260, Vista 64bit. Tried with 2GB and 4GB RAM. Vista was a rather solid OS when I used it. Much more so than XP and 8/8.1.
 
Absolutely love my iPhone 6S Plus. I had a 6 and went to the 6s and the ram increase is very noticeable. I can multitask like no tomorrow and it never bogs down. Say what you want about Apple, but they do a very good job of utilizing available resources.
 
I can't speak for others, but I often end up with a dozen apps open, which I suspect eats a bit of ram (if the apps aren't paged out to the HD. I also suspect there's not a huge cost difference between 4GB and 8GB. Finally, maybe most don't need more than 8GB, but everytime I looked at Laptops, 8GB is the minimum and 16GB is pretty common. 4GB is so 2008 (on the desktop)

Yep, 8GB minimum on laptops and desktops where I work now.

4GB is really no near enough even if you only us MS Office and have a browser open at the same time.
 
I think this is pretty nuts. I have 3GBs (Nexus 6) and am regularly down to ~500MBs free, and I am hardly a big mobile user since I have a good PC. Now if android has some kind of memory management that unloads apps when you get low on ram, that'd be relevant not sure if it does, right now I just use some task killer app when I get low.

Yes, it does manage your RAM. Task killer programs are pointless on Android because it unloads unused data when you need more RAM. And because everything saves when it goes out of RAM you really don't need to be aware of how the memory management works. This means the available RAM metric fairly meaningless because it's all managed by the OS anyway.
 
4gb is common in pcs? what is that writer smoking. I'd love to see someone try to run anything with W7-10 with only 4gb of ram. The OS may load and you can run notepad but a couple chrome tabs and you're out of ram.

Yes, actually, 4GB is common in PCs. The vast majority of PC users are not power users and do not use their computers for playing games. 4GB is the standard amount of RAM in my company's new computers unless their is a specific reason why the user would need more and it ends up being plenty.
 
Yep, 8GB minimum on laptops and desktops where I work now.

4GB is really no near enough even if you only us MS Office and have a browser open at the same time.

Sound's like someone in the IT Department wanted to concoct an excuse to get higher end computers.

If you need 8 gigabytes of RAM for only Office + Web, you are doing it wrong.
 
Except thats not even remotely true. Windows 8 on 2GB is very usable. My tablet with an atom chip and 2gb was perfectly capable of browsing the web with youtube etc. no problems. Played hearthstone well. Having several tabs up on a browser worked just fine.

People need to stop making ignorant assumptions about memory. If you system has excess RAM then most modern desktops will use it. That does not mean that much ram is required to do what you are doing... Just like android phones, just because your system is using 2/3 of your ram does not mean it needs to. Its a lot of pre caching etc. done by the kernel to make it feel a teeny bit snappier.

I cant believe all these ignorant pre conceived notions are still being passed around. Just like the anti vista crowd that cried about memory usage you guys flat out dont know shit about how a modern OS uses memory.

I can tell you right now, if you attempt to use a windows 8 laptop with 2gb of RAM in a business environment (or even 4gb) you will be crawling if you even think about leaving applications open.
 
Truth. The only way a task manager would be useful is if it tagged CPU usage on the applications so you could actually close the one hogging it all. I've had to do that a few times to resolve issues.
 
Sound's like someone in the IT Department wanted to concoct an excuse to get higher end computers.

If you need 8 gigabytes of RAM for only Office + Web, you are doing it wrong.

Many people are going to have:

Office applications (excel, outlook, etc)
Web browser (few tabs in chrome)
Proprietary software the business uses for productivity, payroll or finance
File browser
possibly some streaming service if they allow it

A lot of people leave every single tab they ever open going in chrome nowadays, and it uses an ASSLOAD of RAM.

The single biggest quality of life changes you can do to a laptop for "speed"
-solid state disk
-bump ram from 2 to 4 or 4 to 8GB

All of a sudden it's the fastest computer the user has ever touched.
 
I absolutely hate my iPhone 6 plus. Maybe it was when iOS9 really started to suck??? Regardless, the thing is slow and laggy as hell now.
I've been beta testing iOS 9.2 lately, believe me, iOS 9.2 is miles ahead better than previous versions of iOS 9. 9.2 is what 9.0 should have been from the very beginning. And yes, I blame Apple for the joke that is iOS 9.

The reason why Android phones need ever increasing amounts of RAM is because Google, if you asked me, fucked up in the multitasking department. When you open an app on the phone and you go back to the home screen and launch another app, the app you were working with before is still running in the background? The question is... Why is it still running? It's not in the foreground, it's in the background. Is it doing anything other than just sucking down RAM and CPU? Nope. Then why hasn't it had its state saved and told to go to sleep?

Android users will argue with me about this until Hell freezes over. Android's multitasking system is built upon the same multitasking system that we use on traditional desktop computers. That's fine on a desktop or notebook PC in which you have virtually unlimited computing power and electrical power to run said computing hardware. On a mobile device, you don't have that unlimited computing power or battery power for that matter. So why are we applying a multitasking concept to a device that's inherently limited to begin with? Yeah... when you start to think about it that way you start to wonder why we did it that way.

On Apple iOS when you close a program and go back to the home screen the app has a specified amount of time to finish things up (a minute or so) and then the OS steps in and tells the program that it's going to save the state of the app in question and kill it. That concept works fine for 95% of the apps that most people run because they have no need to be running in the background all the time like they do on Android sucking down battery life, CPU time, and system RAM. Yes, there are some apps that do need to run in the background like music streaming apps, GPS, and others but Apple iOS allows those apps to continue running in the background through a series of multitasking background APIs that Apple doesn't just give to every app that's written. No, that API is only given to apps that present a genuine need to be running in the background and as I stated before, 95% of apps that people use don't need to be running in the background.

If you ask me, I'd much rather have a device that has great battery life that can last all day on a single change than to have the ability to run a whole ton of apps in the background for no good reason and have to search for a power outlet four hours later.
 
I've been beta testing iOS 9.2 lately, believe me, iOS 9.2 is miles ahead better than previous versions of iOS 9. 9.2 is what 9.0 should have been from the very beginning. And yes, I blame Apple for the joke that is iOS 9.

The reason why Android phones need ever increasing amounts of RAM is because Google, if you asked me, fucked up in the multitasking department. When you open an app on the phone and you go back to the home screen and launch another app, the app you were working with before is still running in the background? The question is... Why is it still running? It's not in the foreground, it's in the background. Is it doing anything other than just sucking down RAM and CPU? Nope. Then why hasn't it had its state saved and told to go to sleep?

Android users will argue with me about this until Hell freezes over. Android's multitasking system is built upon the same multitasking system that we use on traditional desktop computers. That's fine on a desktop or notebook PC in which you have virtually unlimited computing power and electrical power to run said computing hardware. On a mobile device, you don't have that unlimited computing power or battery power for that matter. So why are we applying a multitasking concept to a device that's inherently limited to begin with? Yeah... when you start to think about it that way you start to wonder why we did it that way.

On Apple iOS when you close a program and go back to the home screen the app has a specified amount of time to finish things up (a minute or so) and then the OS steps in and tells the program that it's going to save the state of the app in question and kill it. That concept works fine for 95% of the apps that most people run because they have no need to be running in the background all the time like they do on Android sucking down battery life, CPU time, and system RAM. Yes, there are some apps that do need to run in the background like music streaming apps, GPS, and others but Apple iOS allows those apps to continue running in the background through a series of multitasking background APIs that Apple doesn't just give to every app that's written. No, that API is only given to apps that present a genuine need to be running in the background and as I stated before, 95% of apps that people use don't need to be running in the background.

If you ask me, I'd much rather have a device that has great battery life that can last all day on a single change than to have the ability to run a whole ton of apps in the background for no good reason and have to search for a power outlet four hours later.

Good news, There's plenty of android devices that can achieve this, and even ones that can achieve this AND still have a replaceable battery and SD card slot. True multitasking is more similar to a PC user experience and will never change for android devices, it's the way it is and should be. RAM is required for this and it's not a big deal...
 
But why do you need true multitasking on what is a limited usage type device? It has only one screen and apps run in full screen mode. It's not like on a traditional PC in which you can have multiple monitors (if you so wish to do so) and you put one program window into the upper corner and another program window in the lower corner. No, on a mobile device you are limited by the concept that all apps run full screen. So again, the question is... Why do you need true multitasking in that situation? The answer is... You don't.

I would much rather have great battery life that can last all day and not worry about having to charge my phone four hours later or, as you said, have to carry extra batteries and remember to charge them when I get home.
 
Yes, it does manage your RAM. Task killer programs are pointless on Android because it unloads unused data when you need more RAM. And because everything saves when it goes out of RAM you really don't need to be aware of how the memory management works. This means the available RAM metric fairly meaningless because it's all managed by the OS anyway.

Task killer apps hurt performance in Android they don't help. This has been well known since the early days but people just don't listen. This ancient ignorant mentality that an os should use very little ram is to blame. People need to stop thinking they know better and do their homework on how a modern os uses memory.
 
But why do you need true multitasking on what is a limited usage type device? It has only one screen and apps run in full screen mode. It's not like on a traditional PC in which you can have multiple monitors (if you so wish to do so) and you put one program window into the upper corner and another program window in the lower corner. No, on a mobile device you are limited by the concept that all apps run full screen. So again, the question is... Why do you need true multitasking in that situation? The answer is... You don't.

I would much rather have great battery life that can last all day and not worry about having to charge my phone four hours later or, as you said, have to carry extra batteries and remember to charge them when I get home.

Because more and more often that is the device people spend a majority of their time on. My wife uses her iPad and iPhone all day. The only time she opens her laptop is to write papers.

Just because you can't see more than one app at a time doesn't mean multitasking isn't helpful. Whether it is using your browser to look up commands to insert into your ssh terminal or looking up information and using the calculator the ability to do these things seamlessly is valuable.

You can blame crappy battery life on the manufacturers' driven purpose to make phones thinner and thinner because people keep buying the newest shiny.
 
Apologists are out in force defending iOS' brain dead lack of real background multitasking.

Phone is just a pocketable laptop. If I run a SSH/telnet, RDP, VNC, etc. client and put it to the background I want it to stay open like on any other proper computing device and OS.

And, before someone asks why someone you want to do that on a phone. That's because sometimes that's the only device you have on you, for example, when on call or you don't want to be chained to a laptop everywhere you go. Worst thing that can happen is the OS like iOS keeps killing the SSH/telnet session and locking me out of a network device. Also, Android devices can connect to external display and keyboard/mouse unlike iOS.

I get it some people only need a toy iOS phone but to enforce its brain dead limitations on all devices is silly.
 
I really dont understand this mentality. Why are apple users automatically dumb? I go back and forth between android and iOS when i get tired of them and never understood this ridiculously childish way of thinking.

You dont like it so everyone that uses it is automatically less than you are?

You should really sit down and take a minute and think about this way of thinking. Its really not healthy at all.

A year with android and ill start to miss the things iphones offer like the generally good audio components vs androids massively hit or miss audio hardware. Like the audio out from the charge port, why the fuck is it now 8 years into android and this isnt a thing? Apple does a very good job of tightly integrating things together on iOS, the theme and UI is pretty consistent. Android is all over the damned place with UI and themes. iOS as an OS is rock solid, android has always felt like windows XP in the sense that it seems to degrade in performance over time needing a full restore after about 6 months.

Then a year with the iphone and ill get bored of it and want the customization android brings.

I even really like windows phone and would buy those from time to time if they had the app support.

I am so sick of those acting like you are beneath them because of what brand of phone you use. Its disgusting.

This++

I run Windows on my Gaming box
I run Steam on my Linux box along with Ubuntu
My laptops are a Macbook Air & Chromebook
I daily carry with me an Iphone 6 & and LG G Flex 2.

Each has their strenghts & weaknesses. Sticking in "1 camp" doesn't ever let you learn anything new or find the best tool for the job.
 
Apologists are out in force defending iOS' brain dead lack of real background multitasking.

Phone is just a pocketable laptop. If I run a SSH/telnet, RDP, VNC, etc. client and put it to the background I want it to stay open like on any other proper computing device and OS.

And, before someone asks why someone you want to do that on a phone. That's because sometimes that's the only device you have on you, for example, when on call or you don't want to be chained to a laptop everywhere you go. Worst thing that can happen is the OS like iOS keeps killing the SSH/telnet session and locking me out of a network device. Also, Android devices can connect to external display and keyboard/mouse unlike iOS.

I get it some people only need a toy iOS phone but to enforce its brain dead limitations on all devices is silly.

I use a bluetooth keyboard with my ipad mini retina 2 all the time. I also can throwoutput to an external device via either lightning to hdmi connector or appletv. I havent' tried the mouse so I can't comment on it.
 
I use a bluetooth keyboard with my ipad mini retina 2 all the time. I also can throwoutput to an external device via either lightning to hdmi connector or appletv. I havent' tried the mouse so I can't comment on it.

iOS doesn't support mouse so it's useless when docked and used as a laptop replacement to get work done. You have to take your eyes away from the external display, refocus on the tiny phone display and touch it. Brain dead workflow compared to something like this:

DesktopDock_2_600.png
 
iOS doesn't support mouse so it's useless when docked and used as a laptop replacement to get work done. You have to take your eyes away from the external display, refocus on the tiny phone display and touch it. Brain dead workflow compared to something like this:

DesktopDock_2_600.png

Pretty nice doc. What tablet/phones are supported on that?
 
It's sad how the 3GB in the S6/Edge are still inadequate, as is the 8 core CPU. Brb lags during notifications, brb lags during normal usage, brb lags for no reason. Still not sure how you manage to still get so much lag with so much processing power.
 
It's sad how 4GB in the iPad Prosumer synthetic benchmark queen still lags. Only Apple can dumb down an OS and still make it lag.

http://forums.macrumors.com/threads/ipad-pro-lag-issues.1937275/
Again, iOS 9.2 is going to fix all of that. No amount of CPU and RAM can fix bad and/or garbage code. iOS 9.0 and 9.1 stunk on ice. I don't know what the hell Apple did but both of those versions were laggy as all hell.

I've been beta testing iOS 9.2 for quite some time and iOS 9.2 is like a breath of fresh air. Some of the most laggy parts of the user interface like the task switching screen works beautifully now.
 
Because more and more often that is the device people spend a majority of their time on. My wife uses her iPad and iPhone all day. The only time she opens her laptop is to write papers.

Just because you can't see more than one app at a time doesn't mean multitasking isn't helpful. Whether it is using your browser to look up commands to insert into your ssh terminal or looking up information and using the calculator the ability to do these things seamlessly is valuable.

You can blame crappy battery life on the manufacturers' driven purpose to make phones thinner and thinner because people keep buying the newest shiny.

I don't follow. What are those apps doing in the background? Is it something that can't be accomplished, almost instantly, when you bring that app to the foreground?

I'll give an example: if I have a stock app, it could update in the background if multitasking was enabled, but does it really accomplish much vs just updating it when i bring it to the foreground? It save 2 seconds. I'll spend at least a minute scrolling through the stocks. I'd rather not have to think about closing every single app for fear that it'll suck my battery dry (and it doesn't matter how thick the phone is, it's still sucking power without providing any practical value.
 
Again, iOS 9.2 is going to fix all of that. No amount of CPU and RAM can fix bad and/or garbage code. iOS 9.0 and 9.1 stunk on ice. I don't know what the hell Apple did but both of those versions were laggy as all hell.

Heard that excuse too many times before. Someone would claim iOS doesn't lag then actual owners point out lag and the usual defense is, wellllllllllllll, the next iOS version will fix it when in reality it gets more laggy with every release. Been going on since iOS 6 to 7 to 8 to 9. Some think it's Apple's intentional obsolescence to force dumbsumers to upgrade and contribute to the profit$ cycle. Why do you think the newest is called the iPad Pro(fit$)? Smartsumers have a rule to stick with the shipped iOS version for that device and not fall for the downgrade.

Threads like these are common:

http://forums.macrumors.com/threads/ipad-4-and-ios-8-your-experience-please.1817083/

iOS 6 was a pinnacle of speed and stability. My device was fast, fast, fast. That was my first iOS device and I was **in love**.

Then I upgraded to iOS 7 and I lost all of that (not to mention the more attractive design). Then I upgraded to iOS 7.1 and it became a bit better, but still less stable than iOS 6 and far more slower. My god.

iOS 8 is slower than 7.1 even. iOS 8.1 is faster than 8 but slower than 7.1 still.

It’s crazy. Every bit of interface lags. Everything is laggy.
 
Heard that excuse too many times before. Someone would claim iOS doesn't lag then actual owners point out lag and the usual defense is, wellllllllllllll, the next iOS version will fix it when in reality it gets more laggy with every release. Been going on since iOS 6 to 7 to 8 to 9. Some think it's Apple's intentional obsolescence to force dumbsumers to upgrade and contribute to the profit$ cycle. Why do you think the newest is called the iPad Pro(fit$)? Smartsumers have a rule to stick with the shipped iOS version for that device and not fall for the downgrade.

Threads like these are common:

http://forums.macrumors.com/threads/ipad-4-and-ios-8-your-experience-please.1817083/

Overall, I agree, but this is the first time I've had a new iOS noticeably slow down the the previous generation of H/W. My gut says this is a bug. Besides, why would he lie about his experience? It's not like we won't know whenever it comes out.
 
Well I have 4gb on my works laptop, I can barely make it. My problem mostly is on chrome that can take up 1gbs of ram for having 4-6 tabs... I think facebook can eat a lot A LOT of RAM.
 
Google Chrome has been a RAM pig for quite awhile.

It is pretty funny how most of these guys going on about how we need assloads of ram for basic computing keep using Chrome as their examples. Meanwhile i can still rock out FF with a dozen tabs open watching youtube on a windows tablet with 2GB. ;)
 
It's sad how the 3GB in the S6/Edge are still inadequate, as is the 8 core CPU. Brb lags during notifications, brb lags during normal usage, brb lags for no reason. Still not sure how you manage to still get so much lag with so much processing power.

Oh it is very sad. Android has the worst memory management ever.

Too bad in Samsung's documents they didn't include ".. oh and copy Apple's memory management too, ours suck."
 
I don't follow. What are those apps doing in the background? Is it something that can't be accomplished, almost instantly, when you bring that app to the foreground?

I'll give an example: if I have a stock app, it could update in the background if multitasking was enabled, but does it really accomplish much vs just updating it when i bring it to the foreground? It save 2 seconds. I'll spend at least a minute scrolling through the stocks. I'd rather not have to think about closing every single app for fear that it'll suck my battery dry (and it doesn't matter how thick the phone is, it's still sucking power without providing any practical value.

I agree 100%. Ideally when focus is switched away from an app after a period of time it should be paused and saved to memory/flash. Upon switching back it should, with minimum delay, return to -exactly- the same state before being paused. Similar to a virtual machine. In reality I don't think there is any mobile OS where this happens in this fashion. In both iOS and Android apps will go into the background and it is indeterminate if they will return to the same position or not. Like if I am in Firefox/Chrome/Safari and I get an email, read it, respond to it, and come back sometimes the browser will be in the exact place I left it, sometimes the page was purged and needs to be reloaded. Which is frustrating if writing a forum post, filling out a form, or are 2/3 down a long page.

There should be exceptions of course. Options for background pre-loading (like loading an unfocused new tab in a browser) or background services (like AGPS, updates, push notifications, keep-alive, etc). These should be restricted to a reasonable wall time or execution time. But that is just my opinion - I want the best features of desktop and mobile to the extent that is possible.
 
Id like it if you had the option for apps to actually close when you closed them.
 
The problem is 99.9% of apps are garbage, written with less quality control than most PC based programs, which about the same amount are also garbage. But monetizing ideas is more important than executing them well as the markets prove again and again.
 
The problem is 99.9% of apps are garbage, written with less quality control than most PC based programs, which about the same amount are also garbage. But monetizing ideas is more important than executing them well as the markets prove again and again.

That makes sense, as long as it works who cares? Restricting ram or adding ram won't change developers to write better code. The bottom line is the quicker you release the sooner you recoup costs. This is the same iOS, all you have to do is make sure your app doesn't use more than the available amount of memory and it will pass inspection (as long as it works).
 
Android and to lesser extent ios are unoptimized and badly written. Every version of Windows is lighter and faster than the previous one, it's the opposite for mobile os's in general.

At least android is a proper operating system unlike iOS.
 
Back
Top