They're not using the official name of the interstate or highway. It's a simple abbreviation and rarely has ambiguity. It's no different from shortening the name of a street from "21st street" to "21st".
I'd find saying "interstate 10" or "highway 101" every time more awkward and irritating. But this is a "soda" vs. "pop" debate. Until you can't tell what "the 605 North" means because there's some other highway/freeway/etc. with a conflicting name in the same vicinity it's not incorrect. (Further, it's officially named the "San Gabriel River Freeway", not Interstate 605.)
Not all change is good. Much of the change we see is harmful to the language as it introduces ambiguity and causes confusion, which makes it harder for the language to do its only job - help people communicate.
Languages are highly ordered systems. Retards like you are "literally" running about spouting off about doing things "ironically" and are, "for all intensive purposes", entropy endangering the system "irregardless" of your dumbass "language changes" excuse.
NVMe scales. The high end devices today use 4 lanes of PCIe 3.0. There's nothing preventing someone from using (and benefiting from) 16 (or more) lanes of PCIe 4.0 the day that shit is ready to go.
SATA Express was dead before it arrived. M.2 killed it. I still haven't seen a single SATA Express device, though motherboards do have the ports for them. I hope M.2 goes the fuck away. It's a laptop fucking spec and those tiny little shits overheat and throttle because of it. I hope the U.2 shit takes over so we can get high performance 2.5" SSDs with proper housings. (Of course, I'd still prefer they give us 3.5" SSDs but that battle has been lost.)
I do. 4 SSDs in RAID 10 covered that server's performance needs easily and saved a buttload of money. We didn't buy consumer SSDs, we bought the datacenter ones with the longer warranty, extra over provisioning, higher performance, and better TBW. But they're still SATA instead of SAS.
1 TB on the label of a storage device = fuck you, marketers, I know that's just over 0.909 TB.
1 Mb on any networking interface = fuck you, marketers (as usual) and retarded standards bodies (you confused baud and bit ages ago and you're too ashamed to admit your fuckup).
I'm asking him to provide video of his Windows 10 machine NOT instantly BSODing when he plugs in a Kindle. He claimed this was the case. I mentioned the iPhone to avoid any "I can't take video" excuses. You can see below that he admits to making the whole thing up.
LOL! Big fail, bro. The point is this is no mere "bug" that happens randomly to some people, it's yet another example of Windows 10 and MS fucking everything up. So STFU with your defensive bullshit.
It doesn't imply that, it directly states it. It states that the iPhone 6 failure rate is 29%, which is the highest failure rate (among what set of things is unknown).
The main question when picking a new phone is whether to choose an Android one or an iPhone.
I'd wager most people are already tied to an ecosystem. For iOS people it's a question of "When's the new one coming out?" or "Do I want the big one or the small one?". For Android people it's "Do I pick some random cheap one or just buy the Samsung Galaxy again?".
A new study coming from Blancco Technology Group sheds some light on which devices are the most reliable, based on reliability.
Odd, I usually base reliability reports on mouth feel and buoyancy.
The study entitled State of Mobile Device Performance and Health reveals the device failure rates by operating systems, manufacturers, models and regions, as well as the most common types of performance issues.
That would be neat info to have.
The report reveals that in Q2 2016, iOS devices had a 58% failure rate, marking the first time that Apple's devices have a lower performance rate compared to Android.
I wonder how they define "failure rate", maybe I'll read TFA to find out. Wait, "lower performance rate"? WTF is that? Do you mean "higher failure rate". I wonder if this is the fault of the dumbass submitter, TFA, or the actual report. And "first time"? Odd, I've never heard of a prior time that "Blancco Technology Group" released such report. Maybe they're an up-and-comer I should start paying attention to.
It seems that the iPhone 6 had the highest failure rate of 29%, followed by iPhone 6s and iPhone 6S Plus.
Wait, if the highest failure rate is 29%, how do we end up with a 58% failure rate for iOS devices? What subset or subcategory does "iPhone 6" fall under? What "iOS devices" are excluded from that category? Clearly, some significant iOS devices with high failure rates (58% or higher) had to be excluded from the subset/subcategory that gave us the "highest failure rate" of 29%.
Android smartphones had an overall failure rate of 35%, an improvement from 44% in Q1 2016.
So 29% is higher than 35% now? WTF is going on?
Samsung, Lenovo and LeTV were among the manufacturers with the weakest performance and higher failure rates. Samsung scored 26% in failure rate, while Motorola just 11%.
Didn't we just establish an overall failure rate of 35% for Android? Clearly some manufacturer is hitting higher than that, and it's not Samsung. Why would you call out Samsung and not the worst offender?
The study also reveals that iOS devices fail more frequently in North America and Asia compared to Android.
Well, we established that overall, with the "iOS devices had a 58% failure rate" bit at the top and the comments about how Android's failure rate is lower, depending on what contradictory numbers we're looking at.
Specifically, the failure rate in North America is 59%, while in Asia 52%. The failures could be influenced by the fact that the quality of smartphones shipped around the world varies.
Yes, the fact that quality varies in different regions could be due to the fact that the quality of phones varies across different regions! Unless they're suggesting that "quality" and "failure rates" are not directly comparable for the purposes of this study. The only way that could be true is if they didn't control for cause of failure, so "quality" here could mean something along the lines of "survives an American sitting on it" versus "survives an Asian sitting on it".
I want to see the Windows 10 start menu open and close, see whatever shitstain page lists the build number / update level, and then watch you connect a Kindle and have it work.
You said you have an iPhone, so you can easily provide a quick video.
My iPhone rebooted randomly yesterday when I was on the subway.
That's not his point at all, but if a dumb human following software maps and the real world can't do it then an automated car can't either, unless you want it driving on the side walk and through houses.
Pigeons do have good vision and can be trained to do such things (and have, with ball bearings). Your typical BGA package doesn't have thousands of connections, however.
One million? Court can be expensive, but this is a joke of a "case" that Sony would likely never show up to, let alone file. A completely ignorant person could easily defend themselves against such a thing, presuming they're ever actually served, using the free resources available to them. Just ask the clerk of the court. You'd likely be able to recoup your costs as well.
Your honor, this is what we published on that date. It is newsworthy, as it depicts a rumored upcoming product our audience, and many of Sony's current and potential customers, are interested in. We are not bound by any agreement with Sony regarding this information, nor did we commit any crime in obtaining it. If Sony believes a crime was committed we will reveal our source to the court for review, and the court can decide whether or not to release that information to Sony. While Sony has various trademark and copyright claims on the purported products depicted in the video, we were not involved in creating the purported product featuring said trademarks, nor are we involved in selling the purported product (nor has Sony claimed that this product is non-genuine and unfit to bear said trademarks). Further, any copyright claims should be dismissed as this is a clear example of fair use - our articles deal with news, reviews, and critical commentary.
Sure, you'll just grab that bare 7x2mm die with your fingers in your living room, and just plop it down and magically align the hundreds of pins perfectly to the 1 mil traces on the 1 mil thick Kapton board, and then what? Get the Krazy Glue you enjoy huffing?
Still easier and more feasible than repairing anything using BGA.
If you don't use BGA you can inspect visually (accurately, and without X-Rays). This can be done by a human in a second, or by a machine or a pigeon in a fraction of a second.
Slashdot Mirror
They're not using the official name of the interstate or highway. It's a simple abbreviation and rarely has ambiguity. It's no different from shortening the name of a street from "21st street" to "21st".
I'd find saying "interstate 10" or "highway 101" every time more awkward and irritating. But this is a "soda" vs. "pop" debate. Until you can't tell what "the 605 North" means because there's some other highway/freeway/etc. with a conflicting name in the same vicinity it's not incorrect. (Further, it's officially named the "San Gabriel River Freeway", not Interstate 605.)
Not all change is good. Much of the change we see is harmful to the language as it introduces ambiguity and causes confusion, which makes it harder for the language to do its only job - help people communicate.
Languages are highly ordered systems. Retards like you are "literally" running about spouting off about doing things "ironically" and are, "for all intensive purposes", entropy endangering the system "irregardless" of your dumbass "language changes" excuse.
NVMe scales. The high end devices today use 4 lanes of PCIe 3.0. There's nothing preventing someone from using (and benefiting from) 16 (or more) lanes of PCIe 4.0 the day that shit is ready to go.
SATA Express was dead before it arrived. M.2 killed it. I still haven't seen a single SATA Express device, though motherboards do have the ports for them.
I hope M.2 goes the fuck away. It's a laptop fucking spec and those tiny little shits overheat and throttle because of it. I hope the U.2 shit takes over so we can get high performance 2.5" SSDs with proper housings. (Of course, I'd still prefer they give us 3.5" SSDs but that battle has been lost.)
I do. 4 SSDs in RAID 10 covered that server's performance needs easily and saved a buttload of money.
We didn't buy consumer SSDs, we bought the datacenter ones with the longer warranty, extra over provisioning, higher performance, and better TBW. But they're still SATA instead of SAS.
1 TB = 1099511627776 bytes.
1 TiB = fuck you, go back to CS 101.
1 TB on the label of a storage device = fuck you, marketers, I know that's just over 0.909 TB.
1 Mb on any networking interface = fuck you, marketers (as usual) and retarded standards bodies (you confused baud and bit ages ago and you're too ashamed to admit your fuckup).
Dozens of posts have been deleted in the last few years.
Yup. PSA, /. is stagnated.
I'm asking him to provide video of his Windows 10 machine NOT instantly BSODing when he plugs in a Kindle.
He claimed this was the case. I mentioned the iPhone to avoid any "I can't take video" excuses.
You can see below that he admits to making the whole thing up.
LOL! Big fail, bro. The point is this is no mere "bug" that happens randomly to some people, it's yet another example of Windows 10 and MS fucking everything up. So STFU with your defensive bullshit.
It doesn't imply that, it directly states it. It states that the iPhone 6 failure rate is 29%, which is the highest failure rate (among what set of things is unknown).
None of this shit makes any sense!
The main question when picking a new phone is whether to choose an Android one or an iPhone.
I'd wager most people are already tied to an ecosystem. For iOS people it's a question of "When's the new one coming out?" or "Do I want the big one or the small one?". For Android people it's "Do I pick some random cheap one or just buy the Samsung Galaxy again?".
A new study coming from Blancco Technology Group sheds some light on which devices are the most reliable, based on reliability.
Odd, I usually base reliability reports on mouth feel and buoyancy.
The study entitled State of Mobile Device Performance and Health reveals the device failure rates by operating systems, manufacturers, models and regions, as well as the most common types of performance issues.
That would be neat info to have.
The report reveals that in Q2 2016, iOS devices had a 58% failure rate, marking the first time that Apple's devices have a lower performance rate compared to Android.
I wonder how they define "failure rate", maybe I'll read TFA to find out. Wait, "lower performance rate"? WTF is that? Do you mean "higher failure rate". I wonder if this is the fault of the dumbass submitter, TFA, or the actual report. And "first time"? Odd, I've never heard of a prior time that "Blancco Technology Group" released such report. Maybe they're an up-and-comer I should start paying attention to.
It seems that the iPhone 6 had the highest failure rate of 29%, followed by iPhone 6s and iPhone 6S Plus.
Wait, if the highest failure rate is 29%, how do we end up with a 58% failure rate for iOS devices? What subset or subcategory does "iPhone 6" fall under? What "iOS devices" are excluded from that category? Clearly, some significant iOS devices with high failure rates (58% or higher) had to be excluded from the subset/subcategory that gave us the "highest failure rate" of 29%.
Android smartphones had an overall failure rate of 35%, an improvement from 44% in Q1 2016.
So 29% is higher than 35% now? WTF is going on?
Samsung, Lenovo and LeTV were among the manufacturers with the weakest performance and higher failure rates. Samsung scored 26% in failure rate, while Motorola just 11%.
Didn't we just establish an overall failure rate of 35% for Android? Clearly some manufacturer is hitting higher than that, and it's not Samsung. Why would you call out Samsung and not the worst offender?
The study also reveals that iOS devices fail more frequently in North America and Asia compared to Android.
Well, we established that overall, with the "iOS devices had a 58% failure rate" bit at the top and the comments about how Android's failure rate is lower, depending on what contradictory numbers we're looking at.
Specifically, the failure rate in North America is 59%, while in Asia 52%. The failures could be influenced by the fact that the quality of smartphones shipped around the world varies.
Yes, the fact that quality varies in different regions could be due to the fact that the quality of phones varies across different regions! Unless they're suggesting that "quality" and "failure rates" are not directly comparable for the purposes of this study. The only way that could be true is if they didn't control for cause of failure, so "quality" here could mean something along the lines of "survives an American sitting on it" versus "survives an Asian sitting on it".
110010001000 has made several posts about this claiming it shouldn't be a story, is a simple bug, shouldn't be discussed, doesn't happen to him, etc.
He's making a big deal out of it. I'm just calling out his bullshit.
Video proof please.
I want to see the Windows 10 start menu open and close, see whatever shitstain page lists the build number / update level, and then watch you connect a Kindle and have it work.
You said you have an iPhone, so you can easily provide a quick video.
My iPhone rebooted randomly yesterday when I was on the subway.
Put up or shut up.
Not only that, 1.40 on 1 is somehow equal to 1,000,000 on 75,000!
No. It stopped being YOUtube long ago.
Lesser.
Recently featured on The Last Ship, lol.
That's not his point at all, but if a dumb human following software maps and the real world can't do it then an automated car can't either, unless you want it driving on the side walk and through houses.
Just tell them there's a rare Pokemon 100m away.
Fewer.
Pigeons do have good vision and can be trained to do such things (and have, with ball bearings). Your typical BGA package doesn't have thousands of connections, however.
One million? Court can be expensive, but this is a joke of a "case" that Sony would likely never show up to, let alone file. A completely ignorant person could easily defend themselves against such a thing, presuming they're ever actually served, using the free resources available to them. Just ask the clerk of the court. You'd likely be able to recoup your costs as well.
Your honor, this is what we published on that date. It is newsworthy, as it depicts a rumored upcoming product our audience, and many of Sony's current and potential customers, are interested in. We are not bound by any agreement with Sony regarding this information, nor did we commit any crime in obtaining it. If Sony believes a crime was committed we will reveal our source to the court for review, and the court can decide whether or not to release that information to Sony. While Sony has various trademark and copyright claims on the purported products depicted in the video, we were not involved in creating the purported product featuring said trademarks, nor are we involved in selling the purported product (nor has Sony claimed that this product is non-genuine and unfit to bear said trademarks). Further, any copyright claims should be dismissed as this is a clear example of fair use - our articles deal with news, reviews, and critical commentary.
Sure, you'll just grab that bare 7x2mm die with your fingers in your living room, and just plop it down and magically align the hundreds of pins perfectly to the 1 mil traces on the 1 mil thick Kapton board, and then what? Get the Krazy Glue you enjoy huffing?
Still easier and more feasible than repairing anything using BGA.
If you don't use BGA you can inspect visually (accurately, and without X-Rays). This can be done by a human in a second, or by a machine or a pigeon in a fraction of a second.