No recent version includes it natively, regardless of platform, but it will ask you to download if it needs it. I believe the same applies to the libraries needed for BD ripping, but I already had MakeMKV installed, so I'm not sure.
My experience (consistent across multiple machines, not just the one I'm typing on right now) and many, many users posting with stability and performance issues that were introduced with Lion and have persisted since, would seem to disagree with this statement.
That's just false. OSX stability and performance in 10,10 is far far better than say 10.4-6.
My experience (consistent across multiple machines, not just the one I'm typing on right now) and many, many users posting with stability and performance issues that were introduced with Lion and have persisted since. Yes, Apple had bugs before lion, but none that were both performance/stability-affecting and persisted through multiple versions of the OS. That's a new development under Cook, and a very bad sign for those of us who use our machines professionally.
Let's hit your list
... and let's also realize I didn't list every issue. If you want that, I can certainly do it; it'll be one of the longest posts I've ever made here, though.
That's a bug that gets fixed soon. Apple had bugs in 10.2, 10.3, 10.4...
It's been an issue since 10.7. What usability bugs can you point out, pre-10.7, that persisted for multiple releases? I'm honestly asking, since 10.6 was the first version I used.
There were many more bugs in Job’s day.
Shall I provide my comprehensive list? I only listed a handful of the more aggravating issues I've dealt with in the past couple days.
You sound like you have a worm or something, that isn’t OSX.
Then that work shipped on this machine, as the issue persisted when migrating from another machine, despite installing only trusted binaries direct from the developer (e.g. Firefox, Chrome, Adobe stuff, really not a whole hell of a lot else). Considering that this has been an issue for me since the early Yosemite betas (and not before then) and Avast hasn't picked anything up I'm gonna have to say it's not a worm. Especially considering that everyone I know who uses messages and doesn't reboot every other day has the same issue. It's not like it *immediately* uses all of that RAM; in fact, that I refer to it as a memory leak should indicate to you that it behaves as one. It's very well-behaved right now because I just killed and restarted Messages last night, but in a few days it'll be right back up there.
The G4 had terrible throughput for memory and hard drives relative to CPU speed.
And that has what to do with Jobs? He didn't design the CPU; in fact, nobody at Apple did, it was designed and manufactured by IBM, with some manufacturing also being done by Freescale. IBM started making the chips in 1990, 6 years before Jobs' return to Apple. The company was not in a position to pull off an architecture switch in 1996, so the move from G3 to G4 was a logical one; switching to Intel at that time would have killed Apple.
The G5 was excellent but then Jobs wouldn’t commit to a laptop version so just as his CPU problems were fixed he migrated away.
Jobs wouldn't commit to a laptop version because the performance-per-watt just wasn't there. It's hard to sell a laptop with a 45min battery life because the CPU chugs rather than sipping. To top it off, the G5 ran extremely hot and no laptop cooling solution seemed to be able to keep it stable. The final nail in the coffin was IBM's failure to deliver faster chips as they had promised, coupled with their inability to supply enough parts. Freescale wasn't making these chipe, they were all coming from IBM, and IBM wasn't making them fast enough (in either sense of the word) for the desktop sales Apple was seeing; just imagine how things would have gone had they also tried putting them in laptops. Actually, it probably wouldn't have been much of a problem as very few people would have wanted a laptop that melted its casing, overheated, and became unstable; assuming you had it plugged in, as the battery wouldn't have lasted long enough to cause those problems.
The CPU issues were solved when Jobs pushed everyone over to Intel.
I seem to have lost a chunk of my 5th paragraph. The end of that paragraph should read:
Also, really, the extra <4mm of thickness my Nexus 6 brings over the iPhone 6 Plus (my wifes is next to me for comparison) is only in the middle if the curved (to fit your hand) back. A benefit, as it helps you grip it better, the only point my Apple fanboi best frend of over a decade has ever let me have over Apple. Your opinion is welcome (and likely) to differ, but keep in mind that it's only opinion and not fact; it is neither right nor wrong.
I don't care about Apple's applications, I've never used them and I probably never will. I do, however, care about their OS, the stability and performance of which has been degrading steadily since the loss of Jobs. I'm willing to bet most Mac users care about the OS, and that it is stable, even if most don't necessarily need to eek every possible bit of performance out of their machine. Issues like the keyboard and trackpad freezing (external inputs still work; Apple's "fix" is to sleep the computer for a couple minutes, which works about 10% of the time), Messages (which is now part of the OS) using over 2GB of RAM for its own process while making use of another kernel-level process that manages to eat 5GB (watching kernel_task go from over 6GB of RAM to 1.1GB just by closing Messages is freaking silly), that's one hell of a memory leak and there are apparently no plans to fix it. Since Lion, most of the time my mouse cursor disappears after playing a fullscreen video, until I CMD+TAB a few times and I'm not the only one. Still an issue as of Yosemite.
I experienced none of these issues in any version of OS X released while Jobs was active within the company. Lion was released while he was still alive, but his condition had become such that he was no more than a figurehead at that point.
You're absolutely right, though, that Apple's current momentum is coming from Cook. As I said, we're seeing the loss of the last of Jobs' momentum right now. My Jobs-era 17" MBP is absolutely brilliant, despite the GPU defect I had to repair (yes, I work on these machines at that level, so I literally know them inside and out) which is the result of AMD supplying a faulty part. It was even better running Snow Leopard, because if was fast and stable. It has since been replaced as my primary machine, by a 15" MBP Retina, but it's still very much in active use and, upgraded to 16GB or RAM and an SSD, still quite a performant machine. I wish Apple still offered a 17" line, screen real-estate is king for developers and graphic artists. That machine still has better battery life than most mid to mid-high end PC laptops today.
Care to give any examples of what was un-balanced about Apple's machines under Jobs?
As for the iPhone beating Android... 2nd or 3rd in every category isn't beating Android. The players are iPhone, Android, Windows Phone, and Blackberry. Blackberry isn't winning in any of those categories, so placing 3rd means placing behind Android and Windows. Windows isn't pacing ahead of Android anywhere, so placing 2nd means placing behind Android. As for screen quality, Apple hasn't lead that metric for the past 3 years. Yeah, they're winning in thinness (bendability) and weight, for those who like having to check their pocket every couple minutes to make sure they didn't lose their phone; personally, I've switched from lighter prones to heavier ones for that reason. If a weight difference of less than 2 ounces is making your arm tire out any faster, you should go get checked out. Also, really, the extra
The point I'd really like to drive home, though, is this:
The most important reason people buy Apple is the culture of customer base their demand for high quality experiences leads to better applications.
Of course! That's why the OS is rapidly becoming slow and unstable, and major apps that exist on both platforms (like Adobe's suite) are routinely found to perform better on Windows. Wait, no, that's a problem for the kind of user who buys Apple products for what we both agree is the most important reason.
This is what Jobs did for Apple and what Cook is throwing away. As I said earlier, we're losing the all-around experience that people buy Apple for and seeing it replaced with "ooh look, shiiiiiiiiiiiiiny"! We disagree on why that's a good thing; I think it's great that I'll have another chance to buy cheap Apple stock in a few years, since I missed
Indeed. That doesn't mean it's not preferable to giving the phone their full attention. Ideally, their phone should have none of their attention, but we're talking about 'murca here.
Well, yeah if, you decided it was worthwhile to buy into an ecosystem that's locked to a single platform. Personally, while I buy more than a handful of movies each year, the number I (and many others) purchased on iTunes in the two years between then iTunes started selling movies and when Amazon and Google launched their services is a big fat 0. Ripping DVDs has always been an option; and a platform-agnostic and DRM-free option, at that; if you fell into a platform-locked DRM scheme, you should go to the ER and get the gunshot wound in your foot looked at.
I haven't been an AT&T customer for almost 3 years at this point and my wife is the iPhone user so I can only go based on heresay at this point but I'm pretty sure the attwifi network can't be removed.
Also, I'm still on Slashdot, right? I'm asking because there hasn't been any name calling yet.:)
I've seen dongle in a dongle before. Looked painful. And yes, there's a headphone port. That and the USB-C, that's what you get. Did you read the last sentence of my first paragraph, or did you decide you needed to tear that new MacBook apart after my first 12 words? You missed a lot by not reading my whole post, my friend.
More or less, if an attacker knows your home WiFi SSD or can make a lucky guess about what other SSIDs your device might already recognize (e.g. ones that your device was programmed to know out of the box [e.g. attwifi, for 34% of users]), they can name their malicious network in such a way to possibly get you to automatically connect to it as a recognized network.
Hmm...
There's nothing particularly novel about that attack, and contrary to their verbiage, it doesn't force anyone to join a network,...
34% of users can't tell their iPhones not to connect to a hotspot named attwifi. That sounds like the ability to force connection to a WiFi network to me.
... nor can it even easily be used in conjunction with this attack for the vast majority of users.
I'll grant you that, 66% is the vast majority. However...
Is it a potential problem? Absolutely, but only for a small subset of users.
... 34% is not a small subset.
The way they're phrasing it and talking about it, it seems pretty clear that they're trying to boost their own profile a bit.
This I can agree with. It's what lead to the inaccuracy in the summary in the first place.
For most cases, the two attacks can't be used together unless the malicious agent is stalking their victim.
You're right, 66% does constitute "most cases"; 34% of all iPhones sold in the last 3.5 years (that is to say, realistically, damn near 34% of all iPhones currently in use) still seems like a pretty large victim pool, though.
So yes, perhaps the severity of the flaw was a bit overblown by the team that discovered it, but I think you're trying to let out a bit too much of the air.
It's my submission, I'm gonna go out on a limb and say I'm probably not trolling. But, then, that's what a troll would say, isn't it? Cue the next poster who couldn't decide whether to mod me funny or troll, I suppose.:)
I don't see that. What I've seen from Apple for the last 6 years or so has been a shift towards massive innovations in manufacturing and logistics and a move away from a focus on "insanely great" software.
As someone who cares more about how a machine works than how it looks, this is what I have a problem with. I spend hours a day using the software, seconds a day looking at the fit and finish of the machine, and minutes, at most, over the lifetime of the machine looking at the packaging and giving a shit about the logistics of how it got to me. Jobs was focused on the whole experience; today's Apple is focused on "ooh look, shiiiiiiiiny". How can you say were not seeing the loss of Jobs' momentum?
We'll have to wait and see what happens over the next few years; no amount of argument between us will matter.
It was a misunderstanding after my first reading of the article. The actual issue is that the reboot cycle happens so rapidly that you never actually have an opportunity to interact with the phone to turn WiFi off once it starts, until you're out of range of the malicious AP.
Horrible wording in the article that made it not immediately clear, actually. I also posted a correction more than 20 minutes before your "horrible summary" judgment. Also, from the article:
Anyone can take any router and create a Wi-Fi hotspot that forces you to connect to their network
Slashdot Mirror
No recent version includes it natively, regardless of platform, but it will ask you to download if it needs it. I believe the same applies to the libraries needed for BD ripping, but I already had MakeMKV installed, so I'm not sure.
Oh, did I say it was my mistake? Sorry, I meant the editors changed my summary!!
So *every* iPhone screen can light up at the same time? Or so every iPhone user can bitch loudly over the movie at the same time? Perhaps both?
That says nothing of legality and Handbrake works for all the DVDs and BDs I've fed it thus far.
My experience (consistent across multiple machines, not just the one I'm typing on right now) and many, many users posting with stability and performance issues that were introduced with Lion and have persisted since, would seem to disagree with this statement.
That's just false. OSX stability and performance in 10,10 is far far better than say 10.4-6.
My experience (consistent across multiple machines, not just the one I'm typing on right now) and many, many users posting with stability and performance issues that were introduced with Lion and have persisted since. Yes, Apple had bugs before lion, but none that were both performance/stability-affecting and persisted through multiple versions of the OS. That's a new development under Cook, and a very bad sign for those of us who use our machines professionally.
Let's hit your list
... and let's also realize I didn't list every issue. If you want that, I can certainly do it; it'll be one of the longest posts I've ever made here, though.
That's a bug that gets fixed soon. Apple had bugs in 10.2, 10.3, 10.4...
It's been an issue since 10.7. What usability bugs can you point out, pre-10.7, that persisted for multiple releases? I'm honestly asking, since 10.6 was the first version I used.
There were many more bugs in Job’s day.
Shall I provide my comprehensive list? I only listed a handful of the more aggravating issues I've dealt with in the past couple days.
You sound like you have a worm or something, that isn’t OSX.
Then that work shipped on this machine, as the issue persisted when migrating from another machine, despite installing only trusted binaries direct from the developer (e.g. Firefox, Chrome, Adobe stuff, really not a whole hell of a lot else). Considering that this has been an issue for me since the early Yosemite betas (and not before then) and Avast hasn't picked anything up I'm gonna have to say it's not a worm. Especially considering that everyone I know who uses messages and doesn't reboot every other day has the same issue. It's not like it *immediately* uses all of that RAM; in fact, that I refer to it as a memory leak should indicate to you that it behaves as one. It's very well-behaved right now because I just killed and restarted Messages last night, but in a few days it'll be right back up there.
The G4 had terrible throughput for memory and hard drives relative to CPU speed.
And that has what to do with Jobs? He didn't design the CPU; in fact, nobody at Apple did, it was designed and manufactured by IBM, with some manufacturing also being done by Freescale. IBM started making the chips in 1990, 6 years before Jobs' return to Apple. The company was not in a position to pull off an architecture switch in 1996, so the move from G3 to G4 was a logical one; switching to Intel at that time would have killed Apple.
The G5 was excellent but then Jobs wouldn’t commit to a laptop version so just as his CPU problems were fixed he migrated away.
Jobs wouldn't commit to a laptop version because the performance-per-watt just wasn't there. It's hard to sell a laptop with a 45min battery life because the CPU chugs rather than sipping. To top it off, the G5 ran extremely hot and no laptop cooling solution seemed to be able to keep it stable. The final nail in the coffin was IBM's failure to deliver faster chips as they had promised, coupled with their inability to supply enough parts. Freescale wasn't making these chipe, they were all coming from IBM, and IBM wasn't making them fast enough (in either sense of the word) for the desktop sales Apple was seeing; just imagine how things would have gone had they also tried putting them in laptops. Actually, it probably wouldn't have been much of a problem as very few people would have wanted a laptop that melted its casing, overheated, and became unstable; assuming you had it plugged in, as the battery wouldn't have lasted long enough to cause those problems.
The CPU issues were solved when Jobs pushed everyone over to Intel.
Also, really, the extra <4mm of thickness my Nexus 6 brings over the iPhone 6 Plus (my wifes is next to me for comparison) is only in the middle if the curved (to fit your hand) back. A benefit, as it helps you grip it better, the only point my Apple fanboi best frend of over a decade has ever let me have over Apple. Your opinion is welcome (and likely) to differ, but keep in mind that it's only opinion and not fact; it is neither right nor wrong.
I experienced none of these issues in any version of OS X released while Jobs was active within the company. Lion was released while he was still alive, but his condition had become such that he was no more than a figurehead at that point.
You're absolutely right, though, that Apple's current momentum is coming from Cook. As I said, we're seeing the loss of the last of Jobs' momentum right now. My Jobs-era 17" MBP is absolutely brilliant, despite the GPU defect I had to repair (yes, I work on these machines at that level, so I literally know them inside and out) which is the result of AMD supplying a faulty part. It was even better running Snow Leopard, because if was fast and stable. It has since been replaced as my primary machine, by a 15" MBP Retina, but it's still very much in active use and, upgraded to 16GB or RAM and an SSD, still quite a performant machine. I wish Apple still offered a 17" line, screen real-estate is king for developers and graphic artists. That machine still has better battery life than most mid to mid-high end PC laptops today.
Care to give any examples of what was un-balanced about Apple's machines under Jobs?
As for the iPhone beating Android... 2nd or 3rd in every category isn't beating Android. The players are iPhone, Android, Windows Phone, and Blackberry. Blackberry isn't winning in any of those categories, so placing 3rd means placing behind Android and Windows. Windows isn't pacing ahead of Android anywhere, so placing 2nd means placing behind Android. As for screen quality, Apple hasn't lead that metric for the past 3 years. Yeah, they're winning in thinness (bendability) and weight, for those who like having to check their pocket every couple minutes to make sure they didn't lose their phone; personally, I've switched from lighter prones to heavier ones for that reason. If a weight difference of less than 2 ounces is making your arm tire out any faster, you should go get checked out. Also, really, the extra
The point I'd really like to drive home, though, is this:
The most important reason people buy Apple is the culture of customer base their demand for high quality experiences leads to better applications.
Of course! That's why the OS is rapidly becoming slow and unstable, and major apps that exist on both platforms (like Adobe's suite) are routinely found to perform better on Windows. Wait, no, that's a problem for the kind of user who buys Apple products for what we both agree is the most important reason.
This is what Jobs did for Apple and what Cook is throwing away. As I said earlier, we're losing the all-around experience that people buy Apple for and seeing it replaced with "ooh look, shiiiiiiiiiiiiiny"! We disagree on why that's a good thing; I think it's great that I'll have another chance to buy cheap Apple stock in a few years, since I missed
Indeed. That doesn't mean it's not preferable to giving the phone their full attention. Ideally, their phone should have none of their attention, but we're talking about 'murca here.
Excellent point, but I don't think it'd quite be 75%. It would definitely be well above 34% for sure, though.
Handbrake is free and perfectly legal in the US.
Well, yeah if, you decided it was worthwhile to buy into an ecosystem that's locked to a single platform. Personally, while I buy more than a handful of movies each year, the number I (and many others) purchased on iTunes in the two years between then iTunes started selling movies and when Amazon and Google launched their services is a big fat 0. Ripping DVDs has always been an option; and a platform-agnostic and DRM-free option, at that; if you fell into a platform-locked DRM scheme, you should go to the ER and get the gunshot wound in your foot looked at.
I haven't been an AT&T customer for almost 3 years at this point and my wife is the iPhone user so I can only go based on heresay at this point but I'm pretty sure the attwifi network can't be removed.
:)
Also, I'm still on Slashdot, right? I'm asking because there hasn't been any name calling yet.
I've seen dongle in a dongle before. Looked painful. And yes, there's a headphone port. That and the USB-C, that's what you get. Did you read the last sentence of my first paragraph, or did you decide you needed to tear that new MacBook apart after my first 12 words? You missed a lot by not reading my whole post, my friend.
We'll always complain about the summary.
I know Why do you think I keep coming back? ;)
More or less, if an attacker knows your home WiFi SSD or can make a lucky guess about what other SSIDs your device might already recognize (e.g. ones that your device was programmed to know out of the box [e.g. attwifi, for 34% of users]), they can name their malicious network in such a way to possibly get you to automatically connect to it as a recognized network.
Hmm...
There's nothing particularly novel about that attack, and contrary to their verbiage, it doesn't force anyone to join a network, ...
34% of users can't tell their iPhones not to connect to a hotspot named attwifi. That sounds like the ability to force connection to a WiFi network to me.
... nor can it even easily be used in conjunction with this attack for the vast majority of users.
I'll grant you that, 66% is the vast majority. However ...
Is it a potential problem? Absolutely, but only for a small subset of users.
... 34% is not a small subset.
The way they're phrasing it and talking about it, it seems pretty clear that they're trying to boost their own profile a bit.
This I can agree with. It's what lead to the inaccuracy in the summary in the first place.
For most cases, the two attacks can't be used together unless the malicious agent is stalking their victim.
You're right, 66% does constitute "most cases"; 34% of all iPhones sold in the last 3.5 years (that is to say, realistically, damn near 34% of all iPhones currently in use) still seems like a pretty large victim pool, though.
So yes, perhaps the severity of the flaw was a bit overblown by the team that discovered it, but I think you're trying to let out a bit too much of the air.
It's my submission, I'm gonna go out on a limb and say I'm probably not trolling. But, then, that's what a troll would say, isn't it? Cue the next poster who couldn't decide whether to mod me funny or troll, I suppose. :)
That said, I've done it, too. My comment was more a remark about Slashdot's lack of editorial function.
I don't see that. What I've seen from Apple for the last 6 years or so has been a shift towards massive innovations in manufacturing and logistics and a move away from a focus on "insanely great" software.
As someone who cares more about how a machine works than how it looks, this is what I have a problem with. I spend hours a day using the software, seconds a day looking at the fit and finish of the machine, and minutes, at most, over the lifetime of the machine looking at the packaging and giving a shit about the logistics of how it got to me. Jobs was focused on the whole experience; today's Apple is focused on "ooh look, shiiiiiiiiny". How can you say were not seeing the loss of Jobs' momentum?
We'll have to wait and see what happens over the next few years; no amount of argument between us will matter.
How did it take you that long to read the handful of comments that existed at the time?
That said, I've done it, too. My comment was more a remark about Slashdot's lack of editorial function.
There really is no market for the new MacBook. You're absolutely right that there are better machines available for 1/4 the price.
It was a misunderstanding after my first reading of the article. The actual issue is that the reboot cycle happens so rapidly that you never actually have an opportunity to interact with the phone to turn WiFi off once it starts, until you're out of range of the malicious AP.
Anyone can take any router and create a Wi-Fi hotspot that forces you to connect to their network
In other words:
If your WiFi is on...
you're boned.
Indeed, I realized the error upon re-reading the article. If only I could update the summary...
Congrats, you pointed that out a full 21 minutes after the submitter. I'd change it in the summary but, well, Slashdot doesn't allow it.