El Capitan was simply a abortion compared to what used to be a solid OS X. What happened to it Apple???
Not excusing El Capitan, or Apple; but people who have used Apple OSes for longer than a version or two, know that it is best to resist the temptation to Upgrade to a new "Major Release" of OS X until it gets a few "Point Releases" (usually about 4) under its belt.
I suspect the reason for this is not that Apple OS Devs. can't write code; but that Apple, unlike Microsoft, actually pretty much continuously (at least pretty much annually) makes significant changes to OS X (99% of the time in the name of "improvements" or "new features"). This means that, everytime there is a switch from one "Cat" to another (or recently, one "Landmark" to another), a whole bunch of stuff under the hood (and some UI stuff) gets changed. All things being equal, this means that each time that happens, some people run into issues, hate some changes, etc.
Think about it: The parade of new stuff in OS X touted in every WWDC is generally pretty eye-popping. I dare say, other than the reviled Interface-Formerly-Known-As-Metro, there really haven't been as many changes in Windows for the past 4 or 5 Major Releases, as there are in OS X from one Major Release to another.
So, as I said, because of this more rapid progress (and most of it is actually "progress"), most OS X Users "in the know" simply wait a bit until the bugs get ironed out, THEN decide if they want to upgrade.
For example, I'm still rocking 10.9 "Mavericks" on my main MBP; because of the WiFi issues in Yosemite (which finally got ironed out), and the multiple issues in El Capitan, many of which are ironed out as of 10.11.1 (but I'm still going to wait a bit more).
It's the same old story: Those on the bleeding edge occasionally get hurt. And it is still true: Nobody FORCES you to Upgrade. A little common sense (and a look at "history") goes a long way to a happy computing experience, regardless of Platform.
And if you think you "Traded Up" by switching from OS X to Windows 10...
ey come from an era of computing where people were actually expected to know what the fuck they were doing.
Later that same night, Adobe Flash Player got locked out of Safari again so I had to update that, and then I landed up spending another 20 minutes trying to disable SIP on a 10.11 install off an external disk drive because apparently OS X doesn't think you need to be able to write to places like/usr anymore (so much for a Unix-like system).
Simplified form: Boot to Recovery Partition. Open Terminal. Type csrutil disable. Press Return (Enter). Reboot. No more SIP (until you do the opposite (typing csrutil enable, instead).
So much for you knowing "what the fuck [you] were doing, eh?
Mac zealots say we can't get virues, because we have our store. Now the store kicks you out, and viruses can get your certificates. Expect to be ransomed for bitcoins. Meanwhile real operating systems such as GNU/Hurd are unaffected.
But the browser does not correctly page out tab state so entered text and even the scroll position is not saved, it just does a dumb reload. This is something that could and should be improved so I don't see why you're so defensive about it.
Oh, so you've seen the Source code for Mobile Safari? You would have to have done that, since in iOS, each Application is responsible for managing its own memory.
Oh, and two other things: Why does the OP require YOU to fight his battles? And do you not recognize sarcasm when you see it?
And one final thing: I think you will find that I covered the "different use cases" when I suggested that he might be one of those people who just launches Application after Application, until their system grinds to a halt. I've seen it many, many times with both iOS and OSX, because neither OS does a particularly "in your face" job of informing the user about which Apps are actually running.
As for you, I suggest you edumacate yourself on iOS Memory Management. Here's a pretty good discussion regarding same. It explains a lot about why Safari is doing what it's doing under conditions of high RAM pressure, and why iOS doesn't just cache stuff out to a swap file.
My wife's older iPad 2 seems to be having lots of problems with the newer iOS versions in general so we've been thinking of upgrading, but without a guarantee of significantly fewer browser issues I'd seriously consider going with an Android tablet instead.
Nope. If the application has been put in hibernation or has been affected by iOS's memory management strategies (which does happen when you use the multi-tasking features) then when you re-open it and switch to tabs they do indeed reload because it doesn't page the state of the tab to disk when it runs low on resources. Personally it doesn't bother me that much and I prefer to deal with that than the battery life issues that would exist otherwise but let's not pretend it doesn't happen just because it's on the smartphone OS you chose. It's just an OS, dont take its failings as a reflection on you personally.
Ok, you are changing the conditions of the test.
The OP said (or at least implied) that merely switching Tabs (not changing the State of the Application) was enough to cause a Reload of Tabs. He said NOTHING about "Hibernating", "Switching States", etc.
I would expect iOS to reclaim resources when needed, especially from a "Hibernating" App.
I'm not "pretending" about anything. I merely stated that I conducted an admittedly unscientific test, and did not observe the behavior. I wasn't TRYING to "beat" the test; I just tried to duplicate what the OP said/implied, and reported my results, which didn't match his.
That doesn't make me an apologist or a fanboi; just a bad scientist. But then, the OP doesn't win any marks for his (lack of) description of the conditions, which as most of us here know, is ESSENTIAL for testing/troubleshooting a field-reported issue.
It depends on RAM. iOS will pretty aggressively throw away tabs, and reload them when you switch back, if you're low on RAM.
There are other possible implementations of this obviously, and Apple seem to have gone for the simplest. It can be pretty annoying, but Safari on the desktop will often reload pages when you use the back button, which is even worse.
Well, the OP stated this was on an iPhone 6 and 6s; so I assume they have as much RAM as I do with my 6 Plus. I guess, if he is one of those idiots who never "Polices" his open Applications to see if he is running 25 things at a time, then sure, Safari probably marks the memory for inactive Tabs as "unload-able" (sorry, not an iOS dev, don't know the actual term). That would explain it. And as everyone here knows, being in "swapfile" (memory-management) Hell will make ANY system make you want to scream.
And if you say that what Apple has done with memory management regarding Safari Tabs is the "simplest", would you rather that iOS would beat Flash to death using it to shuffle memory pages around? Talk about SLOW... Gotta remember, the Flash that is in Mobile devices is NOT like that which is going into SSDs, as far as write-performance (or endurance) goes.
Safari on iOS is awful, it does exactly as the op said, reloads tabs every time you change. Complete utter crap browser.
If you didn't have your head up your ass you would notice.
And if you didn't have your head up your ass, you'd notice that I stated that I had just tested it.
I had three tabs open (actually many more, but I just tested with 3):
1. A Slashdot Comment Thread.
2. The Slashdot "Stories" Page.
3. A Walmart "product" page.
All three were scrolled-down to a random point, so it would be REALLY obvious if they reloaded.
I clicked back and forth between the three tabs, in no particular order, and each came to the foreground instantly, with NO (perceptible) Reload, and without "losing my place" on the Page.
There are definitely some things that I would like to change a little in Safari Mobile; but unless I'm holding it wrong, I am not seeing what the OP complained about, sorry.
And, although I haven't actually TESTED other Mobile Browsers on iOS or Android, I would venture to guess that they pretty much ALL suck Donkey Dick compared with their Desktop counterparts. It's more about the UI than anything else, and I don't think anybody has gotten that quite right in the Mobile Browser world, on any platform. I've used Chrome on Android a bit, too, and I was wholly unimpressed with it, so, meh...
Which is why it's no use trying to find an alternative to the godawful Safari Mobile. Any other browser available in iOS will suck in the same way, just with some extra suckiness (like less interoperability with other apps) layered on top.
First off: Mods, why is this "Interesting"? It's just complaining.
Second: In what ways SPECIFICALLY is Safari Mobile "Godawful"? Mobile browsers are generally a little-less feature-laden than desktop browsers; but other than that, it seems to do its job fairly well. It took me a little while to get used to the Tab interface; but it certainly isn't "Godawful".
I have an iPhone 6, my wife has a 6s. I hate browsing anything on the junk of a browser found in these supposed pinnacle-of-technology phones. If I have a few tabs open, switching between them reloads the content which wreaks havoc with AJAX websites (or at best I have to scroll and find my location again).
Really? You must have that special version of iOS. The one nobody else has.
I just checked on my iPhone 6 plus, and I was able to tap between several Safari Tabs, and had deliberately scrolled down into the Pages so that it would be easy to see a reload, and in each case, the switching-time was instantaneous, with absolutely NO reloading or re-rendering.
Oh, and iOS' multitasking has nothing to do with this. Stop trying to explain stuff you don't understand.
Ha, ha. Yes, I'm a dumb ass sometimes, my only excuse being that having only very recently upgraded to Yosemite at home and at work, there have been so many other issues to deal with (i.e. just making things bloody well work) that this was one detail that I have put off figuring out. Thanks for saving me the time!
We all can be obtuse beneath our IQs sometimes! Sorry for the semi-snarky response!
To tell you how much I drag my feet with upgrades, I'm still running Mavericks, because I have a BIG Project in Apple Logic that I am afraid to mess up...
FYI, I ALWAYS tell my Apple Friends to WAIT at least a few "point releases" whenever a new version of OS X (or iOS) comes out. It just seems to work out better that way. Back in the MacOS (Classic) days, it seemed like Apple would "test out" their new Frameworks in the LAST "point release" of the PREVIOUS OS Version (so that, e.g., MacOS 6.8 was essentially equivalent to 7.0); so by the time the new "Major" Release came out, things were a lot closer to "just working" (with notable exceptions, to be sure!). But it seems like that has gone by the wayside in OS X.
All iOS web browsers use the WebKit API and don't actually render themselves. Others cheat by rendering on remote servers and showing you the result only, but it's not allowed to contain its own rendering engine.
This is how Chrome on iPad operates - it's not Chrome at all.
Well, you're sort of right. But there have been exceptions to the Rule. In 2010, not only did Apple allow Opera to offer a NON-WebKit iOS Browser (Opera Mini, which later switched to WebKit), although it used Remote Rendering to circumvent the WebKit requirement, but more importantly, in 2014, Apple Released the WkWebView API for iOS 8, which brought the Apple's Nitro Javascript Engine to third-party Browser Development for iOS.
So, these days, third-party Browsers on iOS actually have a fighting chance to be on-par (or maybe even a little better), performance-wise, to Mobile Safari.
"I think if you're looking at a PC, why would you buy a PC anymore? No really, why would you buy one?"
To run ProTools with all the plugins?
Am I the only one who remembers when Apple made machines for creative people? An iPad Pro is useless for them, except for being able to write an email to your parents asking for more money.
I think he meant "PC" as in a WINDOWS PC. I think he thinks of Macs as "Macs", not "Macintosh PCs".
Apple still makes plenty of machines for creative people. MacBook Pros, iMacs, Mac Pros...
But the iPad has a place among creative pros, too, as a quick way to record a musical idea before it is forgotten, as well as a unique type of musical instrument, as well as a MIDI controller, as well as the platform for Apps like Apple's Logic Controller, etc.
Problem with the constant updates and the way Apple is now almost forcing the updates on users is that as in my case just when I have fixed the problems that previous updates to Yosemite caused to some of the software I use (i.e. made the applications completely stop working), they are now more or less forcing El Capitan on me. If and when I do upgrade, it will be a few versions in as earlier versions have caused numerous problem for many people in Mavericks and Yosemite). There must be a way to turn off software update (I am willing to take my chances) as there used to be, but Apple have made it hard to find that option. There are constant update nags that appear in a distracting way at the top right of the monitor. Very annoying...
That was hard. I almost broke a sweat searching for a whole minute through two search results to find the better explanation.;-)
Yes the nags are annoying; but at your own risk, it is good to see that Apple provides a nice, GUI way to stop the madness...
How many viruses (as opposed to trojans and malware that requires user interaction) are there for recent versions of Windows, say 7 through 10? Windows used to leak like a sieve, but Microsoft has put a lot of work into security over the years.
My work W7 laptop (fully patched, running both MSE and Avast!) got drive-by Toolbars and adware-crap in Every single Browser (IE 9, Chrome and FF) except Safari for Windows. And I am VERY careful about not clicking/installing stuff. NONE of these things raised the interest of any of my AV suiteS (plural). And that doesn't even count the weekly AV popups I would get simply out of the blue, JUST because I visited some innocent-looking site, or sometimes seemingly for no reason whatsoever.
Then, a couple of months ago, there was a coworker (again, fully-patched, W7, running MSE and AVG) who SOMEHOW dragged-in a Ransomware virus (again, with NO user intervention required) that walked through our network, encrypting the files on about three of our (again fully patched, MSE and AVG-protected) Windows Servers (these were 2008 R2 and an older 2003 server). If I hadn't had a good backup, we would have been out around 63,000 files.
So yeah, drive-by viruses still exist for "modern" Windows variants. And a I dare you to prove otherwise.
have you clicked and read the descriptions of ANY of those? osx has had just as many of these "viruses that require the user to be stupid AND do most of the virus' work".
btw, does "flashback" ring any bells? it forced apple to remove the "doesn't get pc viruses" from its "why you'll love a mac" page.
Both of your lists show NO Malware that did not rely EXCLUSIVELY on Social Engineering AND DIRECT USER INTERACTION to Infect the host computer (Mac). That is a Trojan, not a Virus.
That is in stark contrast to the Wikipedia list, which nicely categorized the Linux Malware into Trojans, Worms, etc.
Upon Submission, Devs send Apple their XCode Projects, and APPLE does the "For Publication" Build with THEIR (likely non-tainted) copy of XCode. Done!
I'm pretty sure the lawyers at my company (and most closed-source software companies) would say that sending the entire source code to a third party is a non-starter. This could work for open-source software, though.
And I'm pretty sure that your Company's Management would ignore/pressure those Lawyers to find a way to work it out, rather than simply give up the potential Revenues from the hands-down most lucrative Mobile App Platform.
Slashdot Mirror
El Capitan was simply a abortion compared to what used to be a solid OS X. What happened to it Apple???
Not excusing El Capitan, or Apple; but people who have used Apple OSes for longer than a version or two, know that it is best to resist the temptation to Upgrade to a new "Major Release" of OS X until it gets a few "Point Releases" (usually about 4) under its belt.
I suspect the reason for this is not that Apple OS Devs. can't write code; but that Apple, unlike Microsoft, actually pretty much continuously (at least pretty much annually) makes significant changes to OS X (99% of the time in the name of "improvements" or "new features"). This means that, everytime there is a switch from one "Cat" to another (or recently, one "Landmark" to another), a whole bunch of stuff under the hood (and some UI stuff) gets changed. All things being equal, this means that each time that happens, some people run into issues, hate some changes, etc.
Think about it: The parade of new stuff in OS X touted in every WWDC is generally pretty eye-popping. I dare say, other than the reviled Interface-Formerly-Known-As-Metro, there really haven't been as many changes in Windows for the past 4 or 5 Major Releases, as there are in OS X from one Major Release to another.
So, as I said, because of this more rapid progress (and most of it is actually "progress"), most OS X Users "in the know" simply wait a bit until the bugs get ironed out, THEN decide if they want to upgrade.
For example, I'm still rocking 10.9 "Mavericks" on my main MBP; because of the WiFi issues in Yosemite (which finally got ironed out), and the multiple issues in El Capitan, many of which are ironed out as of 10.11.1 (but I'm still going to wait a bit more).
It's the same old story: Those on the bleeding edge occasionally get hurt. And it is still true: Nobody FORCES you to Upgrade. A little common sense (and a look at "history") goes a long way to a happy computing experience, regardless of Platform.
And if you think you "Traded Up" by switching from OS X to Windows 10...
ey come from an era of computing where people were actually expected to know what the fuck they were doing.
/usr anymore (so much for a Unix-like system).
Later that same night, Adobe Flash Player got locked out of Safari again so I had to update that, and then I landed up spending another 20 minutes trying to disable SIP on a 10.11 install off an external disk drive because apparently OS X doesn't think you need to be able to write to places like
This took all of 2 seconds on Google to find.
Simplified form: Boot to Recovery Partition. Open Terminal. Type csrutil disable. Press Return (Enter). Reboot. No more SIP (until you do the opposite (typing csrutil enable, instead).
So much for you knowing "what the fuck [you] were doing, eh?
Or STD's unless you mean Stallmans Toe Diseases
Ewww!
Mac zealots say we can't get virues, because we have our store. Now the store kicks you out, and viruses can get your certificates. Expect to be ransomed for bitcoins. Meanwhile real operating systems such as GNU/Hurd are unaffected.
So, how does it work on Google Play?
That can't be a good idea to make the certificate valid for 20 years.
Why not, since they can be Revoked at any time?
Agreed. The web browser in Android is much much better than the one in iOS.
Hmm. Funny then. Why does this review say differently?
Oh, I know. He must be an Apple shill.
Riiiiight.
But the browser does not correctly page out tab state so entered text and even the scroll position is not saved, it just does a dumb reload. This is something that could and should be improved so I don't see why you're so defensive about it.
Oh, so you've seen the Source code for Mobile Safari? You would have to have done that, since in iOS, each Application is responsible for managing its own memory.
Oh, and two other things: Why does the OP require YOU to fight his battles? And do you not recognize sarcasm when you see it?
And one final thing: I think you will find that I covered the "different use cases" when I suggested that he might be one of those people who just launches Application after Application, until their system grinds to a halt. I've seen it many, many times with both iOS and OSX, because neither OS does a particularly "in your face" job of informing the user about which Apps are actually running.
As for you, I suggest you edumacate yourself on iOS Memory Management. Here's a pretty good discussion regarding same. It explains a lot about why Safari is doing what it's doing under conditions of high RAM pressure, and why iOS doesn't just cache stuff out to a swap file.
My wife's older iPad 2 seems to be having lots of problems with the newer iOS versions in general so we've been thinking of upgrading, but without a guarantee of significantly fewer browser issues I'd seriously consider going with an Android tablet instead.
Have fun!
Nope. If the application has been put in hibernation or has been affected by iOS's memory management strategies (which does happen when you use the multi-tasking features) then when you re-open it and switch to tabs they do indeed reload because it doesn't page the state of the tab to disk when it runs low on resources. Personally it doesn't bother me that much and I prefer to deal with that than the battery life issues that would exist otherwise but let's not pretend it doesn't happen just because it's on the smartphone OS you chose. It's just an OS, dont take its failings as a reflection on you personally.
Ok, you are changing the conditions of the test.
The OP said (or at least implied) that merely switching Tabs (not changing the State of the Application) was enough to cause a Reload of Tabs. He said NOTHING about "Hibernating", "Switching States", etc.
I would expect iOS to reclaim resources when needed, especially from a "Hibernating" App.
I'm not "pretending" about anything. I merely stated that I conducted an admittedly unscientific test, and did not observe the behavior. I wasn't TRYING to "beat" the test; I just tried to duplicate what the OP said/implied, and reported my results, which didn't match his.
That doesn't make me an apologist or a fanboi; just a bad scientist. But then, the OP doesn't win any marks for his (lack of) description of the conditions, which as most of us here know, is ESSENTIAL for testing/troubleshooting a field-reported issue.
It depends on RAM. iOS will pretty aggressively throw away tabs, and reload them when you switch back, if you're low on RAM. There are other possible implementations of this obviously, and Apple seem to have gone for the simplest. It can be pretty annoying, but Safari on the desktop will often reload pages when you use the back button, which is even worse.
Well, the OP stated this was on an iPhone 6 and 6s; so I assume they have as much RAM as I do with my 6 Plus. I guess, if he is one of those idiots who never "Polices" his open Applications to see if he is running 25 things at a time, then sure, Safari probably marks the memory for inactive Tabs as "unload-able" (sorry, not an iOS dev, don't know the actual term). That would explain it. And as everyone here knows, being in "swapfile" (memory-management) Hell will make ANY system make you want to scream.
And if you say that what Apple has done with memory management regarding Safari Tabs is the "simplest", would you rather that iOS would beat Flash to death using it to shuffle memory pages around? Talk about SLOW... Gotta remember, the Flash that is in Mobile devices is NOT like that which is going into SSDs, as far as write-performance (or endurance) goes.
Engineering is ALWAYS about Tradeoffs. Always.
Safari on iOS is awful, it does exactly as the op said, reloads tabs every time you change. Complete utter crap browser. If you didn't have your head up your ass you would notice.
And if you didn't have your head up your ass, you'd notice that I stated that I had just tested it.
I had three tabs open (actually many more, but I just tested with 3):
1. A Slashdot Comment Thread.
2. The Slashdot "Stories" Page.
3. A Walmart "product" page.
All three were scrolled-down to a random point, so it would be REALLY obvious if they reloaded.
I clicked back and forth between the three tabs, in no particular order, and each came to the foreground instantly, with NO (perceptible) Reload, and without "losing my place" on the Page.
There are definitely some things that I would like to change a little in Safari Mobile; but unless I'm holding it wrong, I am not seeing what the OP complained about, sorry.
And, although I haven't actually TESTED other Mobile Browsers on iOS or Android, I would venture to guess that they pretty much ALL suck Donkey Dick compared with their Desktop counterparts. It's more about the UI than anything else, and I don't think anybody has gotten that quite right in the Mobile Browser world, on any platform. I've used Chrome on Android a bit, too, and I was wholly unimpressed with it, so, meh...
Which is why it's no use trying to find an alternative to the godawful Safari Mobile. Any other browser available in iOS will suck in the same way, just with some extra suckiness (like less interoperability with other apps) layered on top.
First off: Mods, why is this "Interesting"? It's just complaining.
Second: In what ways SPECIFICALLY is Safari Mobile "Godawful"? Mobile browsers are generally a little-less feature-laden than desktop browsers; but other than that, it seems to do its job fairly well. It took me a little while to get used to the Tab interface; but it certainly isn't "Godawful".
I have an iPhone 6, my wife has a 6s. I hate browsing anything on the junk of a browser found in these supposed pinnacle-of-technology phones. If I have a few tabs open, switching between them reloads the content which wreaks havoc with AJAX websites (or at best I have to scroll and find my location again).
Really? You must have that special version of iOS. The one nobody else has.
I just checked on my iPhone 6 plus, and I was able to tap between several Safari Tabs, and had deliberately scrolled down into the Pages so that it would be easy to see a reload, and in each case, the switching-time was instantaneous, with absolutely NO reloading or re-rendering.
Oh, and iOS' multitasking has nothing to do with this. Stop trying to explain stuff you don't understand.
Ha, ha. Yes, I'm a dumb ass sometimes, my only excuse being that having only very recently upgraded to Yosemite at home and at work, there have been so many other issues to deal with (i.e. just making things bloody well work) that this was one detail that I have put off figuring out. Thanks for saving me the time!
We all can be obtuse beneath our IQs sometimes! Sorry for the semi-snarky response!
To tell you how much I drag my feet with upgrades, I'm still running Mavericks, because I have a BIG Project in Apple Logic that I am afraid to mess up...
FYI, I ALWAYS tell my Apple Friends to WAIT at least a few "point releases" whenever a new version of OS X (or iOS) comes out. It just seems to work out better that way. Back in the MacOS (Classic) days, it seemed like Apple would "test out" their new Frameworks in the LAST "point release" of the PREVIOUS OS Version (so that, e.g., MacOS 6.8 was essentially equivalent to 7.0); so by the time the new "Major" Release came out, things were a lot closer to "just working" (with notable exceptions, to be sure!). But it seems like that has gone by the wayside in OS X.
He was like a mad Keith Richards gone Tin Pot Dictator.
GREAT Imagery!
Nothing.
All iOS web browsers use the WebKit API and don't actually render themselves. Others cheat by rendering on remote servers and showing you the result only, but it's not allowed to contain its own rendering engine.
This is how Chrome on iPad operates - it's not Chrome at all.
Well, you're sort of right. But there have been exceptions to the Rule. In 2010, not only did Apple allow Opera to offer a NON-WebKit iOS Browser (Opera Mini, which later switched to WebKit), although it used Remote Rendering to circumvent the WebKit requirement, but more importantly, in 2014, Apple Released the WkWebView API for iOS 8, which brought the Apple's Nitro Javascript Engine to third-party Browser Development for iOS.
So, these days, third-party Browsers on iOS actually have a fighting chance to be on-par (or maybe even a little better), performance-wise, to Mobile Safari.
What kind of moron thinks becoming a shitty copy-cat of something kicking your ass is a good idea.
I dunno. It seems like Windows has been doing that with OS X for years now.
Hasn't FF become the laughingstock of the Browser world?
It used to be the King; but it seems like it has Vulnerabilities galore, and is a Resource Hog to boot.
As an iOS user, HONESTLY, what is compelling here over Mobile Safari?
To run ProTools with all the plugins?
Am I the only one who remembers when Apple made machines for creative people? An iPad Pro is useless for them, except for being able to write an email to your parents asking for more money.
I think he meant "PC" as in a WINDOWS PC. I think he thinks of Macs as "Macs", not "Macintosh PCs".
Apple still makes plenty of machines for creative people. MacBook Pros, iMacs, Mac Pros...
But the iPad has a place among creative pros, too, as a quick way to record a musical idea before it is forgotten, as well as a unique type of musical instrument, as well as a MIDI controller, as well as the platform for Apps like Apple's Logic Controller, etc.
Problem with the constant updates and the way Apple is now almost forcing the updates on users is that as in my case just when I have fixed the problems that previous updates to Yosemite caused to some of the software I use (i.e. made the applications completely stop working), they are now more or less forcing El Capitan on me. If and when I do upgrade, it will be a few versions in as earlier versions have caused numerous problem for many people in Mavericks and Yosemite). There must be a way to turn off software update (I am willing to take my chances) as there used to be, but Apple have made it hard to find that option. There are constant update nags that appear in a distracting way at the top right of the monitor. Very annoying...
That was hard. I almost broke a sweat searching for a whole minute through two search results to find the better explanation. ;-)
Yes the nags are annoying; but at your own risk, it is good to see that Apple provides a nice, GUI way to stop the madness...
How many viruses (as opposed to trojans and malware that requires user interaction) are there for recent versions of Windows, say 7 through 10? Windows used to leak like a sieve, but Microsoft has put a lot of work into security over the years.
My work W7 laptop (fully patched, running both MSE and Avast!) got drive-by Toolbars and adware-crap in Every single Browser (IE 9, Chrome and FF) except Safari for Windows. And I am VERY careful about not clicking/installing stuff. NONE of these things raised the interest of any of my AV suiteS (plural). And that doesn't even count the weekly AV popups I would get simply out of the blue, JUST because I visited some innocent-looking site, or sometimes seemingly for no reason whatsoever.
Then, a couple of months ago, there was a coworker (again, fully-patched, W7, running MSE and AVG) who SOMEHOW dragged-in a Ransomware virus (again, with NO user intervention required) that walked through our network, encrypting the files on about three of our (again fully patched, MSE and AVG-protected) Windows Servers (these were 2008 R2 and an older 2003 server). If I hadn't had a good backup, we would have been out around 63,000 files.
So yeah, drive-by viruses still exist for "modern" Windows variants. And a I dare you to prove otherwise.
have you clicked and read the descriptions of ANY of those? osx has had just as many of these "viruses that require the user to be stupid AND do most of the virus' work".
btw, does "flashback" ring any bells? it forced apple to remove the "doesn't get pc viruses" from its "why you'll love a mac" page.
http://www.welivesecurity.com/... http://securitywatch.pcmag.com...
Are you stoned or just stupid?
Both of your lists show NO Malware that did not rely EXCLUSIVELY on Social Engineering AND DIRECT USER INTERACTION to Infect the host computer (Mac). That is a Trojan, not a Virus.
That is in stark contrast to the Wikipedia list, which nicely categorized the Linux Malware into Trojans, Worms, etc.
NEXT!
That is all.
Upon Submission, Devs send Apple their XCode Projects, and APPLE does the "For Publication" Build with THEIR (likely non-tainted) copy of XCode. Done!
I'm pretty sure the lawyers at my company (and most closed-source software companies) would say that sending the entire source code to a third party is a non-starter. This could work for open-source software, though.
And I'm pretty sure that your Company's Management would ignore/pressure those Lawyers to find a way to work it out, rather than simply give up the potential Revenues from the hands-down most lucrative Mobile App Platform.
The parent AC.
Oh, sorry!
Thanks!