Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Says the guy who can't even prove i'm wrong.

Typical logical fallacy. Try and switch the Burden of Proof to someone to prove them wrong, instead of proving yourself right.

Read again, when we are talking about multitasking, it's from what the users can do and not what the OS HAS to do to work in the first place.

Sorry, as a developer I only consider one definition of multitasking. Not something you (or Samsung) fabricate to fool people into believing it means something else.

Yeah, you have some extremely few apps that you can use in multitasking mode. Question is, why are so many app for iOS not using that feature?

No, the question is why a brand-new S7 can't even keep up with a 3 year old 5S when I want to multitask something in real time (without latency). Now that's what I call pathetic.

Or why there are so many 64bit Android phones but there's no 64bit software to take advantage of them. Google made a huge mistake telling developers for years to use the SDK and code in Java instead of the NDK and C/C++. Now we have a bunch of Java Apps that can't take advantage of a 64bit processor.
 
  • Like
Reactions: SockRolid
Or why there are so many 64bit Android phones but there's no 64bit software to take advantage of them. Google made a huge mistake telling developers for years to use the SDK and code in Java instead of the NDK and C/C++. Now we have a bunch of Java Apps that can't take advantage of a 64bit processor.

This.

VM's don't scale well in a multitasking environment.
The main advantage of iOS is and has always been Obj-C and its really small runtime.

Now, it is Swift and its compiler based on LLVM that was heavily influenced by Apple.
This advantage is hard to compete with, regardless of the current state of iOS from a GUI perspective.
 
  • Like
Reactions: EricTheHalfBee
I just pointed out that you can run like 4 apps actively at the same time and switch between them with those small bubbles you can turn an app into when you minimizes them without getting the apps to go into a pause mode. You can however only run 2 apps in a multiwindow though.

But in reality, you can run as many apps actively in the background as you would like to as long as there is enough RAM for that.
This isnt useful to me. I actually prefer to have the additional battery life.
 
I'm kind of confused on why I would want so many apps open on my iPhone.

On the other hand my iPad air 2 is more useful in this sense as I can do safari split window (IOS 10 beta), split apps, watch video while browsing.

So apple will pick and choose what makes sense, I definitely think the Plus model should get split apps in landscape mode.
 
Typical logical fallacy. Try and switch the Burden of Proof to someone to prove them wrong, instead of proving yourself right.
Again, ask anyone what they say multitasking is when you looks at a normal users perspective. The answer here is simple and you don't have to be a rocket scientist to figure that out.

Sorry, as a developer I only consider one definition of multitasking. Not something you (or Samsung) fabricate to fool people into believing it means something else.
To bad for you then. And no, the thing that you as a normal user have to do several things at the same time (like in multiwindow) is not something I or Samsung have fabricated. It's something that is logic. I as a human doesn't do multitasking because i can breathe and look at the same time. I do multitasking when i can do a phone call and drive at the same time as an example.

No, the question is why a brand-new S7 can't even keep up with a 3 year old 5S when I want to multitask something in real time (without latency). Now that's what I call pathetic.
Everyone with a brain and IQ higher than a monkey knows that this is nothing but a flat out lie. A Galaxy S7 destroys the iPhone 6S Plus in everything except for one thing. And that one thing is speed. But then, there is much more to a smartphone today than just speed. I'm just saying.

Or why there are so many 64bit Android phones but there's no 64bit software to take advantage of them. Google made a huge mistake telling developers for years to use the SDK and code in Java instead of the NDK and C/C++. Now we have a bunch of Java Apps that can't take advantage of a 64bit processor.
There is alot of apps today that uses 64-bit architecture. You are just bad at looking for apps that supports that. Not only that, but Android smartphones today have 4 GB or more RAM which will need a 64-bit CPU in the first place when the RAM get's over 4 GB.
[doublepost=1470754299][/doublepost]
This isnt useful to me. I actually prefer to have the additional battery life.
Then tell Apple to give you a bigger battery that will last you longer than some few hours then maybe?

Samsung's high end phones at least have a big battery that makes up for those functionality the phones have.
 
Last edited:
  • Like
Reactions: macintoshi
Again, ask anyone what they say multitasking is when you looks at a normal users perspective. The answer here is simple and you don't have to be a rocket scientist to figure that out.

To bad for you then. And no, the thing that you as a normal user have to do several things at the same time (like in multiwindow) is not something I or Samsung have fabricated. It's something that is logic. I as a human doesn't do multitasking because i can breathe and look at the same time. I do multitasking when i can live as a human and drive at the same time as an example.

No, it was clever marketing from Samsung. The term "true multitasking" didn't really take off until Samsung started marketing it with their Note series and having two Apps side-by-side. I have to give Samsung credit for changing the definition of multiwindow to multitasking just so they could claim Apple doesn't have it. Brilliant marketing that fooled a lot of gullible people (including you).

Everyone with a brain and IQ higher than a monkey knows that this is nothing but a flat out lie. A Galaxy S7 destroys the iPhone 6S Plus in everything except for one thing. And that one thing is speed. But then, there is much more to a smartphone today than just speed. I'm just saying.

Sorry, 100% true. I'm sorry that the fact the 6S from 11 months ago is a better all-round performer than the flagship S7 with their mega 8-core processor. I'm also sorry it bothers you so much. As to the rest - the S7 camera is only "slightly" better than the 6S, but when out taking quick snaps (like people do) they are essentially the same. On the video side the 6S is clearly superior. The 6S (and even the lowly SE) can even do 1080P 120FPS slo-motion, which the S7 lacks the horsepower to do.


There is alot of apps today that uses 64-bit architecture. You are just bad at looking for apps that supports that. Not only that, but Android smartphones today have 4 GB or more RAM which will need a 64-bit CPU in the first place when the RAM get's over 4 GB.

Here we go again. I'll repeat this as it doesn't seem to sink in:

Anyone who uses the 4GB RAM argument when talking about 64bit processors should be put on ignore, because it's painfully obvious they know nothing about 64bit processing. This is a myth that has been debunked countless times. The fact you still believe this explains your ignorance in the other topics of this thread.
 
  • Like
Reactions: John Mcgregor
Again, ask anyone what they say multitasking is when you looks at a normal users perspective. The answer here is simple and you don't have to be a rocket scientist to figure that out.


To bad for you then. And no, the thing that you as a normal user have to do several things at the same time (like in multiwindow) is not something I or Samsung have fabricated. It's something that is logic. I as a human doesn't do multitasking because i can breathe and look at the same time. I do multitasking when i can do a phone call and drive at the same time as an example.

Everyone with a brain and IQ higher than a monkey knows that this is nothing but a flat out lie. A Galaxy S7 destroys the iPhone 6S Plus in everything except for one thing. And that one thing is speed. But then, there is much more to a smartphone today than just speed. I'm just saying.


There is alot of apps today that uses 64-bit architecture. You are just bad at looking for apps that supports that. Not only that, but Android smartphones today have 4 GB or more RAM which will need a 64-bit CPU in the first place when the RAM get's over 4 GB.
[doublepost=1470754299][/doublepost]
Then tell Apple to give you a bigger battery that will last you longer than some few hours then maybe?

Samsung's high end phones at least have a big battery that makes up for those functionality the phones have.
A bigger battery doesn't necessarily mean better battery life. I only care about battery life more than multitasking. You are never going to be doing more than one thing at a time on your iPhone anyway. Secondly, there may be other technical constraints that wouldnt allow for a larger battery.
 
No, it was clever marketing from Samsung. The term "true multitasking" didn't really take off until Samsung started marketing it with their Note series and having two Apps side-by-side. I have to give Samsung credit for changing the definition of multiwindow to multitasking just so they could claim Apple doesn't have it. Brilliant marketing that fooled a lot of gullible people (including you).
Again, look up what 'multitasking' is when you looks at that via a normal users perspective on what that is and what that does. Samsung is spot on on explaining why their phones can do 'REAL' multitasking, because running 2 apps at the same time is considered 'real multitasking' from a user perspective. In the exact same way as we humans do multitasking when we drives a car and do a phone call at the same time. If you only do one of those things, you are no longer multitasking.

Sorry, 100% true. I'm sorry that the fact the 6S from 11 months ago is a better all-round performer than the flagship S7 with their mega 8-core processor. I'm also sorry it bothers you so much. As to the rest - the S7 camera is only "slightly" better than the 6S, but when out taking quick snaps (like people do) they are essentially the same. On the video side the 6S is clearly superior. The 6S (and even the lowly SE) can even do 1080P 120FPS slo-motion, which the S7 lacks the horsepower to do.
Did you miss the thing i said that there is ALOT more to a phone today than just speed?

Yeah omg, the iPhone 6S Plus is a little faster than a Galaxy S7 edge. Who cares as the iPhones can't do crap compared to the Galaxy S7 edge anyways?

You are comparing a drag race car that is extremely fast at going directly forward, but extremely bad at taking a turn. A Galaxy S7 edge is a hypercar with alot of technology and enhancement that really make the car a joy to use everywhere, even though it's not as fast as a drag race car.

Here we go again. I'll repeat this as it doesn't seem to sink in:

Anyone who uses the 4GB RAM argument when talking about 64bit processors should be put on ignore, because it's painfully obvious they know nothing about 64bit processing. This is a myth that has been debunked countless times. The fact you still believe this explains your ignorance in the other topics of this thread.
Tell me exactly what the 64-bit apps do that makes the users go wow over it?

When the iPhone got the 64-bit CPU, there was no visible differences or made the apps any faster by going from 32 to 64-bit apps for the normal users. However, it made alot of differences for the app developers though.
[doublepost=1470756421][/doublepost]
A bigger battery doesn't necessarily mean better battery life. I only care about battery life more than multitasking. You are never going to be doing more than one thing at a time on your iPhone anyway. Secondly, there may be other technical constraints that wouldnt allow for a larger battery.
Well, i can't really say my battery life on my Galaxy S6 edge+ is bad with it's 3000 mAh battery though ;).

1: https://dl.dropboxusercontent.com/u/7309753/Mobiltelefoner/Samsung Galaxy S6 edge+/Bilder/Screenshot_2016-01-29-06-32-07.png

2: https://dl.dropboxusercontent.com/u/7309753/Mobiltelefoner/Samsung Galaxy S6 edge+/Bilder/Screenshot_2016-01-29-06-32-22.png

One day and an almost 5 hours of usage with almost 6 hours screen on time. That's pretty darn good. But that's not all.

3: https://dl.dropboxusercontent.com/u/7309753/Mobiltelefoner/Samsung Galaxy S6 edge+/Bilder/Screenshot_2016-02-07-17-09-31.png

4: https://dl.dropboxusercontent.com/u/7309753/Mobiltelefoner/Samsung Galaxy S6 edge+/Bilder/Screenshot_2016-02-07-17-09-45.png

Two and a half day usage with 4 hours and 33 mins with screen on time is extremely good.
 
Last edited:
  • Like
Reactions: macintoshi
Again, look up what 'multitasking' is when you looks at that via a normal users perspective on what that is and what that does. Samsung is spot on on explaining why their phones can do 'REAL' multitasking, because running 2 apps at the same time is considered' real multitasking' from a user perspective. In the exact same way as we humans do multitasking when we drives a car and do a phone call at the same time. If you only do one of those things, you are no longer multitasking.

No it's not. Multitasking from a user perspective is doing one task while another is performing in the background (like downloading files or playing music while working on a Word document or browsing the Internet). It has nothing to do with multi-windows.


Did you miss the thing i said that there is ALOT more to a phone today than just speed?

Did you miss the part where this thread is about processors and performance? Why are you trying (failing) to derail the topic to things not related to processors/performance?

Yeah omg, the iPhone 6S Plus is a little faster than a Galaxy S7 edge. Who cares as the iPhones can't do crap compared to the Galaxy S7 edge anyways?

You are comparing a drag race car that is extremely fast at going directly forward, but extremely bad at taking a turn. A Galaxy S7 edge is a hypercar with alot of technology and enhancement that really make the car a joy to use everywhere.

Tell me exactly what the 64-bit apps do that makes the users go wow over it?

When the iPhone got the 64-bit CPU, there was no visible differences or made the apps any faster by going from 32 to 64-bit apps for the normal users. However, it made alot of differences for the app developers though.

I can edit 4K video on my 6S. On the S7 you have to find a third party App to do so, and they are terrible. My 6S is way faster at editing a 4K clip then all the Apps I tried on my S7. But feel free to recommend me a 4K editor for Android, and if I haven't already tried it then I'll download it to compare speed.

I can do real-time transposition on my 5S (which the S7 can't do). That's because the App I use is a native 64bit App and not something written in Java.

As I already mentioned above (and you missed) the 6S can shoot 1080P at 120FPS. This requires the ability to process a LOT of imaging data in real time. Something a 64bit processor (with the proper software) excels at.

When the iPhone 5S came out within 1 week Algoriddim produced a 64bit App called djay 2. They literally took their 64bit optimized code from their Mac version and were able to port it over to the iPhone. This allowed them to do real-time processing and effects that were not possible on mobile devices previously. To this day, even the S7 version of djay 2 can't do real-time processing that the 5S from 3 years ago could.

And this is where iOS has the advantage. Android doesn't have a desktop OS equivalent that people can port their code over from. iOS developers can reuse code from Mac software to bring desktop level features to iOS. Windows developers could also do this. Android can't, because it's a stand-alone system that doesn't have a "parent" desktop OS (and no, Linux doesn't count because Android is so far removed from Linux it's barely recognizable anymore).


I'm so sorry you're stuck using the inferior, insecure Android with its Apps written in that kiddie language Java that can't even make use of that 64bit processor you have.
 
  • Like
Reactions: John Mcgregor
A bigger battery doesn't necessarily mean better battery life. I only care about battery life more than multitasking. You are never going to be doing more than one thing at a time on your iPhone anyway. Secondly, there may be other technical constraints that wouldnt allow for a larger battery.

Not doing more than one thing is true, but that doesn't mean we don't need more than one app working at the same time in true multitasking fashion. Unfortunately, our phones with 1GB of RAM truly suck in this regard. Run out of RAM and the app will be reloaded the next time it is selected and whatever form data was inputed will be lost. Unfortunately again, this isn't difficult to do with just Safari and one other app open lol.

iOS multitasking still pales in comparison to any desktop OS due to the power constraints. With so little RAM I can't guarantee switching apps will preserve data between apps. Oh wait, I need to buy a new iPhone with more RAM to enjoy "true" multitasking.
 
Looks like Apple are still prioritising single core performance over cramming in a million cores into a mobile CPU.

As they should, everything that can be done in multi core, can be done in one single core. Many algorithms have to be done by a single core and cannot be multi core. Also, there are overheads if you are going to parelelize.

As the master himself:

If you were plowing a field, which would you rather use? Two strong oxen or 1024 chickens?

Seymour Cray
 
No it's not. Multitasking from a user perspective is doing one task while another is performing in the background (like downloading files or playing music while working on a Word document or browsing the Internet). It has nothing to do with multi-windows.
But then, try to download something in the background and then open another app on iOS on the iPhone. If the download stops up then, then it's no multitasking. Aka what you describe is not possible on iPhones with iOS. So your point is moot.

And no, it's not YOU AS A USER who does the multitasking if you believe the background processes in IOS are considered multitasking for the users. We the users have to do multiple things in the OS at the same time before WE as users can do multitasking. It's about what us users can do and not what the OS has to do to work.

Did you miss the part where this thread is about processors and performance? Why are you trying (failing) to derail the topic to things not related to processors/performance?
Processors and performance is also about the speed if you aren't aware. Because you know, there is no points at all to give the users a new processor if the performance and the speed isn't better, you know?

I can edit 4K video on my 6S. On the S7 you have to find a third party App to do so, and they are terrible. My 6S is way faster at editing a 4K clip then all the Apps I tried on my S7. But feel free to recommend me a 4K editor for Android, and if I haven't already tried it then I'll download it to compare speed.
And what argument was the iOS fanboys using earlier when we said that iOS was missing features and things?

Yes, you said 'there is always an app for that'. Now i'm gonn use that argument against the iOS fanboys on this and say that we also have an app for that, so it's all fine.

I can do real-time transposition on my 5S (which the S7 can't do). That's because the App I use is a native 64bit App and not something written in Java.
Do you have any proofs on that, or are you just dicating up false statements here to defend Apple?

As I already mentioned above (and you missed) the 6S can shoot 1080P at 120FPS. This requires the ability to process a LOT of imaging data in real time. Something a 64bit processor (with the proper software) excels at.
1080p @ 120 fps is a nice thing to have. But i'm afraid 96% of everyone who uses an iPhone doesn't cares about that as most of those are only posting short 10 seconds clips on Snapchat or some short video clips on YouTube or even posting crappy images on Instagram / Facebook anyways.

There is only some very few peoples that cares about 60 and 120 / 240 fps video recording. Those who cares about that are usually making more serious videos to begin with.

Actually, the last video i made was recorded in 4k resolution with 30 fps. Because what i was video recording doesn't need 60 or 120 fps to look good. Infact, here is the video.....


When the iPhone 5S came out within 1 week Algoriddim produced a 64bit App called djay 2. They literally took their 64bit optimized code from their Mac version and were able to port it over to the iPhone. This allowed them to do real-time processing and effects that were not possible on mobile devices previously. To this day, even the S7 version of djay 2 can't do real-time processing that the 5S from 3 years ago could.
I would like to see a proof of that statement when it's about djay 2 on Android.

And this is where iOS has the advantage. Android doesn't have a desktop OS equivalent that people can port their code over from. iOS developers can reuse code from Mac software to bring desktop level features to iOS. Windows developers could also do this. Android can't, because it's a stand-alone system that doesn't have a "parent" desktop OS (and no, Linux doesn't count because Android is so far removed from Linux it's barely recognizable anymore).
This is an advantage for the app developers and no direct advantage for the casual user. Again, see the difference from what the users want's to what the app developers needs.


I'm so sorry you're stuck using the inferior, insecure Android with its Apps written in that kiddie language Java that can't even make use of that 64bit processor you have.
Android is as secure as it can be as long as you are not going outside of the Play Store. It's a proven fact.

Yeah, Android do have some security holes from time to time, but who doesn't?

There doesn't exists an OS that is malware / virus proof anyways.
 
But then, try to download something in the background and then open another app on iOS on the iPhone. If the download stops up then, then it's no multitasking. Aka what you describe is not possible on iPhones with iOS. So your point is moot.

Sorry, you're a liar, plain and simple. I download things in the background on iOS regularly (with another App running in the foreground). The fact you claim it's not possible on iOS leads me to believe you're nothing but a liar and a troll. And I don't waste my time trying to educate people who are only here to tell lies.
 
@EricTheHalfBee

As a developer I understand what multitasking means in the classical sense. Due to the iPhone's puny power constraints Apple distinguishes between changing apps and allowing an app to refresh itself in the background.

From Apple's support page:

You can quickly switch from one app to another on your iOS device. When you switch back, you can pick up right where you left off.

That statement isn't entirely true. Pure marketing speak.

Apple then continues with discussing Background App Refresh. Now this feature is how we think of multitasking in the classical sense, but this has to be activated on a per application basis for 3rd party apps. I'd argue that with multitasking in the classical sense there is no distinction between changing apps and allowing an app to refresh itself in the background.

That doesn't mean iOS isn't a multitasking OS. This was obvious from the very beginning where it was possible to use a web browser while playing music in the background. Too bad Apple prioritized thinness over making iOS more enjoyable to use. But nope, I need to think about what I'm doing before switching apps. When I switch back what I'm working on may be gone.
 
Sorry, you're a liar, plain and simple. I download things in the background on iOS regularly (with another App running in the foreground). The fact you claim it's not possible on iOS leads me to believe you're nothing but a liar and a troll. And I don't waste my time trying to educate people who are only here to tell lies.
Ok, if you go into Spotify and download a big playlist for offline use and then goes out of the app and into another app. If the download of the playlist for Spotify here stops up then in the background, there my points still stands.

Or maybe you should prove me to be wrong here before you call me a liar?

I know i'm 100% correct here.
 
  • Like
Reactions: macintoshi
Apple could deliver the fastest processor ever in a smartphone.

And people would complain that it looks the same as their previous phones.

I dunno... I'd rather have the chip engineers get a good workout instead of the designers.

There's that old saying: "It's what's on the INSIDE that counts" :)

And it's actually worse, because when Apple releases the fastest processor ever in a smartphone people will still quote number of cores and clock speed before they look at performance.
 
  • Like
Reactions: Michael Scrip
Sorry, you're a liar, plain and simple. I download things in the background on iOS regularly (with another App running in the foreground). The fact you claim it's not possible on iOS leads me to believe you're nothing but a liar and a troll. And I don't waste my time trying to educate people who are only here to tell lies.

I recall that downloading in the background wasn't always possible. I recall they introduced this feature in iOS 7. Also, I believe apps have to be updated to use this feature.
[doublepost=1470761768][/doublepost]
And it's actually worse, because when Apple releases the fastest processor ever in a smartphone people will still quote number of cores and clock speed before they look at performance.

I think Apple should concentrate on how people use their phones. Samsung has hammered this point home to good effect. Which reminds me how much better their selfie camera is...
 
... Android is as secure as it can be as long as you are not going outside of the Play Store. It's a proven fact.

Yeah, Android do have some security holes from time to time, but who doesn't?

There doesn't exists an OS that is malware / virus proof anyways.

Proven fact? Give us a reference. Otherwise it's just wishful thinking.

Oh, and have you heard? New QuadRooter vulnerabilities that affect 900 million Android devices.
If the device uses the Qualcomm chipset, it's at risk:

http://blog.checkpoint.com/2016/08/07/quadrooter/

Google just doesn't care. 97% of Google's revenue comes from ads.
They are an advertising company. They exist to service their advertisers.
 
  • Like
Reactions: EricTheHalfBee
Proven fact? Give us a reference. Otherwise it's just wishful thinking.

Oh, and have you heard? New QuadRooter vulnerabilities that affect 900 million Android devices.
If the device uses the Qualcomm chipset, it's at risk:

http://blog.checkpoint.com/2016/08/07/quadrooter/

Google just doesn't care. 97% of Google's revenue comes from ads.
They are an advertising company. They exist to service their advertisers.

I wouldn't go that far as to say Google doesn't care. You should see how many security bugs their Project Zero team finds in iOS. Google doesn't design its own hardware yet and it can't control their OEMs, but that's an entirely different conversation.
 
Proven fact? Give us a reference. Otherwise it's just wishful thinking.

Oh, and have you heard? New QuadRooter vulnerabilities that affect 900 million Android devices.
If the device uses the Qualcomm chipset, it's at risk:

http://blog.checkpoint.com/2016/08/07/quadrooter/

Google just doesn't care. 97% of Google's revenue comes from ads.
They are an advertising company. They exist to service their advertisers.
The Play Store app vertify is already killing the QuadRooter vulnerability which is an extra security on top of Android. So again, if you are inside the Play Store, you are safe. Because you have to manually install an app to get the QuadRooter malware. And that wont come from Play Store, that's for sure.

EDIT: It's proven to be correct: http://www.androidcentral.com/google-confirms-verify-apps-can-block-apps-quadrooter-exploits
 
Not doing more than one thing is true, but that doesn't mean we don't need more than one app working at the same time in true multitasking fashion. Unfortunately, our phones with 1GB of RAM truly suck in this regard. Run out of RAM and the app will be reloaded the next time it is selected and whatever form data was inputed will be lost. Unfortunately again, this isn't difficult to do with just Safari and one other app open lol.

iOS multitasking still pales in comparison to any desktop OS due to the power constraints. With so little RAM I can't guarantee switching apps will preserve data between apps. Oh wait, I need to buy a new iPhone with more RAM to enjoy "true" multitasking.
Multitasking on phones sucks in general. It's not exclusive to iOS. You are either wasting your battery or your are pretending to multitask which you really aren't doing anyway by any stretch of the imagination. It still just amounts to running stuff in the background and my iPhone has 2gig of ram but either way I want the apps to be in the background not wasting large amounts of battery. My phone lasts like a day and a half or more as a result under normal usage including safari browsing, facebook, twitter, messaging and email and music.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.