USDOT does regulate at the Federal level, my friend. Did you forget that? States may choose not to enforce, but that doesn't mean the regulations hold no weight.
Oh, yes, and let's make it illegal to lie when answering that question. Surely, that will work in all the places where using a phone while driving is already illegal but people do it anyway. Right?
Right? And, actually, having the alerts is quite useful. One or two messages in a short period? It can wait until I get where I'm going. Alerts flooding in? Possibly a server down somewhere, I should probably find a place to pull over so I can deal with it. Give me a phone that doesn't bother to alert me just because I might be driving and I'll thank you for the paperweight, then hand it back to you as I already have enough of those.
I view cars and guns in very much the same manner; both can be used to kill a whole lot of people. I feel the same way about most "safety" features in cars, as well: if you can't drive without them, you shouldn't drive; if you drive with them, you'll become dependent on them and will be totally screwed if you ever have to drive without them. Again, likewise for guns; manual safeties and magazine disconnects give people the feeling that a firearm can be made safe to point at another human being and pull the trigger without consequence, until one of those safeties fails or they pick up a gun that lacks those safeties and they don't know it.
Do I think people who can't respect the power over life and death afforded to them by a vehicle should not be behind the wheel of a vehicle? In very much the same way I believe someone who can't respect the power over life and death afforded to them by a gun shouldn't be behind the barrel of a gun (but, perhaps, in front of it), YES. Do I think the general population should be denied these freedoms? With the already-stated exceptions, NO.
In fact, let's make this simple and apply the same logic to anything else that could be dangerous.
It's called situational awareness and personal responsibility (it used to be called common sense, back when it was actually common) and it's severely lacking around here anymore.
Then, in most jurisdictions, this wouldn't be a problem in the first place. Most places in the US, where this article is relevant, cell phone use while driving is already illegal.
Having played Pokemon Go, that feature is what actually broke the game for my wife and I. When one of us was driving, the other would handle both phones, and it worked well until that feature, which had the habit of resetting after every stop (or arbitrarily on the freeway when your speed hadn't dropped below 65MPH).
I don't know if they've fixed that, but I do know my wife and I have stopped hopping in the car on the weekends to drive to more densely populated areas where we could walk around and catch Pokemon while we talk about all the things that happened during the week that we didn't get to talk about earlier. We still talk about that stuff, but now it happens on the couch; she's not into fitness walking which means, if I want to still have that time with her, I also had to give it up.
Thanks, Niantic, for single-handedly striking a blow against physical fitness, right after you showed how much of a positive impact you were capable of.
I agree, while apps can implement that feature, anyone who brings it up should kindly fuck off and never speak of it again.
Actually, what parent said is precisely what Trump said he will do. Since he has to sign off on these regulations, he can, ultimately, enforce that. Which two regulations does this bill repeal? None? No signature.
We can't fix stupid, but nature provided us with a cure from day one. Not content with limiting early death incidents to only the stupid, we invented ways to keep them from killing themselves before they could harm others.
Ironically, some of the worst cowboy coders I've worked with have been Professional Engineers...
I'm not sure that's irony; the most likely explanation seems quite logical to me. When they put on their (credentialed) engineer hat, they must follow strict procedures or face heavy consequences; when they take it off, they can finally relax, so they do.
And, at any rate, "memory" is a misnomer, as it is actually referring to flash storage, rather than RAM. Yes, still technically memory, but more akin to an SSD than what people typically think of when they hear the word "memory". It would have no bearing whatsoever on network throughput.
You're pretending every single phone they make has to be replaced under warranty?
If you'd read my entire post, you'd see that I address that very point. You, on the other hand, implied that the cost applied to every phone; or, at least, failed to address the fact that it does not.
And chiding me for making shit up? Really? It's the middle of my work day, I don't have time to look up the actual numbers, but I do happen to know the numbers I made up are much closer to reality than the numbers you made up. Be careful with that stone in that glass house.
So the phone originally cost Apple $260 to make, then costs another $350 to replace under warranty, and they only get to keep $495 of the $695 retail price of the original sale? So... The cost to Apple of the original sale, plus replacement, is $610 and they only get $495 of that original sale? So they're assuming a $115 loss (before facilities, taxes, and paryoll) on every 32GB iPhone 7 sold?
Nah, I think the reality is more along the lines of: we're looking at a BOM cost built using retail pricing rather than Apple's bulk pricing, or even what you could get parts for at a Shenzhen market. Think closer to $50 in parts and $65 for the warranty replacement, with the retailer getting $150 of the retail price; Apple gets to keep closer to $430 of the retail price. Also, remember that Apple has been working on Campus 2, a $5B expenditure, since 2010; not all of that $5B is attributed to the iPhone, let alone the iPhone 7. None of the remaining $10B in facilities is attributed to the iPhone. The total labor cost of an iPhone by the time it reaches EOP (remember, each unit reduces the non-manufacturing portion of this cost) is around $30. We'll circle back around to facilities in a moment, but I want to clarify that, after labor, Apple still has $400 of that retail price in their pocket; call it $399, landed.
Now, Apple will sell 75 million iPhones this year, which will net them just over $29.9B after materials, labor, and shipping. Even if they had to pay their entire facilities cost out of that, they'd have a profit of nearly $15B.
Double the manufacturing labor cost ($20 -> $40), which increases the overall labor cost per unit to $50 and they still pull in just over $28.4B before facilities. Double the entire cost (including that warranty replacement) and they make $19.8B before facilities. Worst case, if they had to pay for all $15B of facilities costs out of one year of iPhone sales, they're still left with $4.8B in profit for the iPhone alone; that's what they'd be taxed on.
Of course, since the warranty replacement rate on the iPhone is less than 100%, I did not factor in Apple Care, and I only considered the 32GB model (which represents the lowest profit margin), my numbers are a bit low.
Ah, I see, you think having to keep connectors and adapters on-hand and make sure you remember to bring them with you everywhere you might need them is a zero-sum event.
I mean, sure, for Mac users who connected their machines to RS-232 devices, dropping the RS-422 was practically a zero-sum event, since they still needed the same number of dongles. Except in cases where the USB RS-232 adapters fucked with timing-sensitive applications; in those cases, the lack of an RS-422 or RS-232 port meant the machine was useless for the intended application. There's a reason you can still find brand new machines with RS-232 ports; even the best USB to RS-232 adapters fuck with timing to some degree.
But, requiring a different dongle where one was already required is not "EXACTLY like" requiring a dongle where one was not previously required. To paraphrase, I happen to know you're smart enough to realize that.
Incidentally, this was perfectly acceptable on the iMac, as it was with the MacBook, as these are consumer devices; by its very name, the MacBook Pro is a professional machine. As such, it must be suited for immediate, no hassle, use in a wide variety of professional settings, which it is most certainly not. Seriously, the MacBook Air has better connectivity; that's just fucked up. Period.
At any rate, it didn't bother me until I learned that the MacBook Pro seems to have problems with wi-fi with a USB-C device is connected and exhibits display issues when a Thunderbolt 3 display adapter is present. Unfortunately, since that's all the connectivity the machine has, that means it can't walk and chew gum at the same time. Slow down (or lose entirely) my network connectivity while I transfer files to or from a drive? Nah. I'll just keep my real professional machine and have the drive plugged in and accessible at all times, thank you. And by "real professional machine", I mean 2013 model MacBook Pro; oh, and the 2013 model MSI gaming laptop I also use for the same purpose... and the recently-built AMD workstation I'm currently sitting at. These are machines capable of operating in a professional capacity; the new MacBook "Pro" is not.
The port was developed in 1994 by an Intel-lead team and was available on machines as early as 1995. Windows 95 did support BIOS-controlled (driverless) PS/2 keyboard and mouse input and that's precisely what my 1995 PC exposed to the OS when a USB keyboard or mouse was plugged in. I do think you're correct about the scanner, I may not have had that until some years later; it was originally connected to that machine, though.
You watched Apple ditch a serial port only used by Apple and a drive interface that most vendors aside form Apple had already largely moved away from and adopt a port that was largely invented by Intel (with no input from Apple, mind you) 3 years after it first appeared on PCs and you think that's Apple revolutionizing the industry?
HA!
And yes, I had one of those PCs back in 1995, along with a USB keyboard, mouse, and scanner, so I know it's true.
Yes, an adapter for the projector, no big deal because you had other ports to plug everything else into without adapters. There is an HDMI and/or displayport adapter permanently attached to the projector in nearly every conference room I've been in, so it is really never necessary to carry one; though I always do because I know the one time I don't I'll need it.
Now? Adapters! Adapters for EVERYTHING! Such glory!!!
Slashdot Mirror
Right. Does that stop anyone?
Right. And the same people who use their phones while driving where it is already illegal to do so will suddenly start turning on driving mode?
USDOT does regulate at the Federal level, my friend. Did you forget that? States may choose not to enforce, but that doesn't mean the regulations hold no weight.
And fuck Facebook for their recent ad campaign laden with vertical video!
Oh, yes, and let's make it illegal to lie when answering that question. Surely, that will work in all the places where using a phone while driving is already illegal but people do it anyway. Right?
I feel like AC meant both.
Right? And, actually, having the alerts is quite useful. One or two messages in a short period? It can wait until I get where I'm going. Alerts flooding in? Possibly a server down somewhere, I should probably find a place to pull over so I can deal with it. Give me a phone that doesn't bother to alert me just because I might be driving and I'll thank you for the paperweight, then hand it back to you as I already have enough of those.
So so so VERY much THIS! YES!
I view cars and guns in very much the same manner; both can be used to kill a whole lot of people. I feel the same way about most "safety" features in cars, as well: if you can't drive without them, you shouldn't drive; if you drive with them, you'll become dependent on them and will be totally screwed if you ever have to drive without them. Again, likewise for guns; manual safeties and magazine disconnects give people the feeling that a firearm can be made safe to point at another human being and pull the trigger without consequence, until one of those safeties fails or they pick up a gun that lacks those safeties and they don't know it.
Do I think people who can't respect the power over life and death afforded to them by a vehicle should not be behind the wheel of a vehicle? In very much the same way I believe someone who can't respect the power over life and death afforded to them by a gun shouldn't be behind the barrel of a gun (but, perhaps, in front of it), YES. Do I think the general population should be denied these freedoms? With the already-stated exceptions, NO.
In fact, let's make this simple and apply the same logic to anything else that could be dangerous.
It's called situational awareness and personal responsibility (it used to be called common sense, back when it was actually common) and it's severely lacking around here anymore.
Then, in most jurisdictions, this wouldn't be a problem in the first place. Most places in the US, where this article is relevant, cell phone use while driving is already illegal.
CanadianMacFan's point is spot-on.
Having played Pokemon Go, that feature is what actually broke the game for my wife and I. When one of us was driving, the other would handle both phones, and it worked well until that feature, which had the habit of resetting after every stop (or arbitrarily on the freeway when your speed hadn't dropped below 65MPH).
I don't know if they've fixed that, but I do know my wife and I have stopped hopping in the car on the weekends to drive to more densely populated areas where we could walk around and catch Pokemon while we talk about all the things that happened during the week that we didn't get to talk about earlier. We still talk about that stuff, but now it happens on the couch; she's not into fitness walking which means, if I want to still have that time with her, I also had to give it up.
Thanks, Niantic, for single-handedly striking a blow against physical fitness, right after you showed how much of a positive impact you were capable of.
I agree, while apps can implement that feature, anyone who brings it up should kindly fuck off and never speak of it again.
Actually, what parent said is precisely what Trump said he will do. Since he has to sign off on these regulations, he can, ultimately, enforce that. Which two regulations does this bill repeal? None? No signature.
We can't fix stupid, but nature provided us with a cure from day one. Not content with limiting early death incidents to only the stupid, we invented ways to keep them from killing themselves before they could harm others.
Bravo, humanity.
Ironically, some of the worst cowboy coders I've worked with have been Professional Engineers...
I'm not sure that's irony; the most likely explanation seems quite logical to me. When they put on their (credentialed) engineer hat, they must follow strict procedures or face heavy consequences; when they take it off, they can finally relax, so they do.
And, at any rate, "memory" is a misnomer, as it is actually referring to flash storage, rather than RAM. Yes, still technically memory, but more akin to an SSD than what people typically think of when they hear the word "memory". It would have no bearing whatsoever on network throughput.
You're pretending every single phone they make has to be replaced under warranty?
If you'd read my entire post, you'd see that I address that very point. You, on the other hand, implied that the cost applied to every phone; or, at least, failed to address the fact that it does not.
And chiding me for making shit up? Really? It's the middle of my work day, I don't have time to look up the actual numbers, but I do happen to know the numbers I made up are much closer to reality than the numbers you made up. Be careful with that stone in that glass house.
So the phone originally cost Apple $260 to make, then costs another $350 to replace under warranty, and they only get to keep $495 of the $695 retail price of the original sale? So... The cost to Apple of the original sale, plus replacement, is $610 and they only get $495 of that original sale? So they're assuming a $115 loss (before facilities, taxes, and paryoll) on every 32GB iPhone 7 sold?
Nah, I think the reality is more along the lines of: we're looking at a BOM cost built using retail pricing rather than Apple's bulk pricing, or even what you could get parts for at a Shenzhen market. Think closer to $50 in parts and $65 for the warranty replacement, with the retailer getting $150 of the retail price; Apple gets to keep closer to $430 of the retail price. Also, remember that Apple has been working on Campus 2, a $5B expenditure, since 2010; not all of that $5B is attributed to the iPhone, let alone the iPhone 7. None of the remaining $10B in facilities is attributed to the iPhone. The total labor cost of an iPhone by the time it reaches EOP (remember, each unit reduces the non-manufacturing portion of this cost) is around $30. We'll circle back around to facilities in a moment, but I want to clarify that, after labor, Apple still has $400 of that retail price in their pocket; call it $399, landed.
Now, Apple will sell 75 million iPhones this year, which will net them just over $29.9B after materials, labor, and shipping. Even if they had to pay their entire facilities cost out of that, they'd have a profit of nearly $15B.
Double the manufacturing labor cost ($20 -> $40), which increases the overall labor cost per unit to $50 and they still pull in just over $28.4B before facilities. Double the entire cost (including that warranty replacement) and they make $19.8B before facilities. Worst case, if they had to pay for all $15B of facilities costs out of one year of iPhone sales, they're still left with $4.8B in profit for the iPhone alone; that's what they'd be taxed on.
Of course, since the warranty replacement rate on the iPhone is less than 100%, I did not factor in Apple Care, and I only considered the 32GB model (which represents the lowest profit margin), my numbers are a bit low.
Amazon Web Services, Microsoft Azure and IBM's Bluemix all already offer GPU as a service.
They still make great Linux machines if you don't install the graphics driver and don't mind the garbled pre-GRUB boot screen.
Those would be words exchanged "at the time of exchanging money for goods/services", so you tell me.
Ah, I see, you think having to keep connectors and adapters on-hand and make sure you remember to bring them with you everywhere you might need them is a zero-sum event.
I mean, sure, for Mac users who connected their machines to RS-232 devices, dropping the RS-422 was practically a zero-sum event, since they still needed the same number of dongles. Except in cases where the USB RS-232 adapters fucked with timing-sensitive applications; in those cases, the lack of an RS-422 or RS-232 port meant the machine was useless for the intended application. There's a reason you can still find brand new machines with RS-232 ports; even the best USB to RS-232 adapters fuck with timing to some degree.
But, requiring a different dongle where one was already required is not "EXACTLY like" requiring a dongle where one was not previously required. To paraphrase, I happen to know you're smart enough to realize that.
Incidentally, this was perfectly acceptable on the iMac, as it was with the MacBook, as these are consumer devices; by its very name, the MacBook Pro is a professional machine. As such, it must be suited for immediate, no hassle, use in a wide variety of professional settings, which it is most certainly not. Seriously, the MacBook Air has better connectivity; that's just fucked up. Period.
At any rate, it didn't bother me until I learned that the MacBook Pro seems to have problems with wi-fi with a USB-C device is connected and exhibits display issues when a Thunderbolt 3 display adapter is present. Unfortunately, since that's all the connectivity the machine has, that means it can't walk and chew gum at the same time. Slow down (or lose entirely) my network connectivity while I transfer files to or from a drive? Nah. I'll just keep my real professional machine and have the drive plugged in and accessible at all times, thank you. And by "real professional machine", I mean 2013 model MacBook Pro; oh, and the 2013 model MSI gaming laptop I also use for the same purpose... and the recently-built AMD workstation I'm currently sitting at. These are machines capable of operating in a professional capacity; the new MacBook "Pro" is not.
Lenovo... LOL
The port was developed in 1994 by an Intel-lead team and was available on machines as early as 1995. Windows 95 did support BIOS-controlled (driverless) PS/2 keyboard and mouse input and that's precisely what my 1995 PC exposed to the OS when a USB keyboard or mouse was plugged in. I do think you're correct about the scanner, I may not have had that until some years later; it was originally connected to that machine, though.
You watched Apple ditch a serial port only used by Apple and a drive interface that most vendors aside form Apple had already largely moved away from and adopt a port that was largely invented by Intel (with no input from Apple, mind you) 3 years after it first appeared on PCs and you think that's Apple revolutionizing the industry?
HA!
And yes, I had one of those PCs back in 1995, along with a USB keyboard, mouse, and scanner, so I know it's true.
Yes, an adapter for the projector, no big deal because you had other ports to plug everything else into without adapters. There is an HDMI and/or displayport adapter permanently attached to the projector in nearly every conference room I've been in, so it is really never necessary to carry one; though I always do because I know the one time I don't I'll need it.
Now? Adapters! Adapters for EVERYTHING! Such glory!!!
Window 10 has been serving me well since it came out. Linux has been serving me well for two decades. You make many assumptions, friend.