That's like saying to a software developer that he/she doesn't need to understand what memory leaks and segfault exceptions are, and how to prevent/fix them, because it's the job of the compiler to compile code in a way such that software never crashes.
And in a sandboxed, garbage-collected language, that would be exactly correct.
It's time for HDL developers to hold their tool vendors to the same standards that software developers expect.
But if you can't draw a K-map and cover glitch cases, just as one example, then you are not qualified to develop programmable logic.
Of course you are. That's what the tools are for. Nobody writing HDL needs to mess with Karnaugh maps, and once the tools get a bit smarter, they won't have to worry about domain-crossing glitches either.
*Wow, who is making the argument that we should "sacrifice free speech for a better society"? That sounds positively Orwellian. Or something from China, where the government runs a massive censorship operation.*
Read the comments in the NYT article. There are hundreds of them demanding just that. It's the scariest thing I've read in quite some time.
That's not a typo mistake. Sure enough, you are not intelligent as you think you are.
Not being very smart, I'll have to leave this word salad up to others to parse.
This gives me an idea, though. Perhaps the dumbshit programmers at Apple and Google should offer separate modes for their mobile operating systems: beginner, normal, and advanced. Copious text bubbles and prompts to explain and confirm various actions in beginner mode, some swipe actions disabled. Normal mode is similar to what is delivered now. And an advanced mode with more swipe actions akin to how keyboard shortcuts are used in desktop applications.
The "send my voice" feature is an example of something that should not be enabled by default, given the half-assed way it's implemented. Unfortunately, the centralized Settings menu tree is another weak point of modern iOS versions. Bury it in Settings and it might as well be lost forever. IMHO it's time to start associating Settings / Options buttons with individual applications again.
I'd probably put the "send my voice" button on an alternate keyboard or otherwise hide it. It's not a first-rank feature, and it shouldn't be in a position to be easily activated by mistake.
It happened. I don't blame you, I didn't believe it either.
Of course I knew the mic button existed, I use it all the time to dictate text messages. And I sometimes hit it accidentally, being a klutz. But in past versions of iOS, it's always been sufficient to hit 'Done' to make the mic UI go away. It has never decided on its own that, since it didn't recognize any valid speech, I must have wanted to record and attach an audio clip.
Sure, it's a nifty feature, as far as features go, but the failings are obvious: it should have asked me to confirm the attachment, or at least given me some indication that an attachment was being created. To the best of my recollection, there was no indication of that until after it was too late to remove the waveform attachment. (I'd say there's a 5% chance I'm wrong about that, as I wasn't paying that much attention.)
The other day I discovered a new iOS feature I had no idea existed. While sending a text to a customer, I hit the microphone icon by mistake. Another person in the (parked, idling) car was muttering about how the customer was a moron, which, although true enough, wasn't something I intended to include as part of the text. Not hard to see where this story is going, right? Well, it's even dumber than you're thinking.
I hit the 'Done' button to make the voice input UI go away, finished the text message, and hit 'Send.' As far as I knew, there was no danger that my friend's comment would be added to the text message. The car was too noisy and her voice was too low.for the speech recognition engine to understand, and in any event, the "moron" comment didn't appear in the outgoing text message. No problem.
Except what did appear in the text message, visible only after I sent it, was a small attachment balloon with a waveform. Apparently, iOS now sends the captured audio file as a binary attachment if it can't extract any recognizable speech.
So the obvious question is, what kind of drugs are these people taking? Is no one at a Fortune 500 company capable of thinking anything through these days? Do the programmers who think these features are "cool": and "awesome" not have managers with a three-digit IQ?
Fortunately for me, my phone lost its signal right about then, and I was able to kill the text app while it was still displaying "Sending." I knew from experience that iOS's text app didn't attempt to provide guaranteed delivery, and sure enough, when I restarted it, it had forgotten all about the message it was trying to send. So in a sense, I was saved by the same dumbshit programmers at Apple who tried to ruin my day.
It seems we have to adopt the same attitude around microphones that we normally apply to firearms. The gun is always loaded, and the mike is always live.
Lightspeed was terribly careless when it came to dealing with regulation
Yeah, they should have hired at least one attorney or at least one engineer who could tell the MBAs, "No, we can't use internationally-allocated satellite-to-ground spectrum for terrestrial communications."
But it's a lot easier to blame the big bad gubbermint.
Even if it is a self-driving car, a seat that 100 other people have sat in recently is still gross, and you can't ever clean it properly without replacing the seats often.
But nobody would have cared if California had Oklahoma's population density. No harm would have been observed, certainly not at a scale that would prompt the creation of the Clean Air Act and a cabinet-level agency to enforce it. Mother Nature can absorb a certain amount of pollution of any kind... just not at California scale.
There are probably more cars in Los Angeles County alone (population 10 million) than in the entire state of Oklahoma (population 4 million).
*If it were just a local issue, then we could put 100 coal power plants in the middle of nowhere and it wouldn't matter. But ultimately they reduce the air quality everywhere over time.*
Quantity has a quality all its own. 100 coal plants is not a major problem for anyone not living next to one of them. 100,000 is everybody's problem.
Even in the 70s, someone who was educated and understood the problem knew that equipment was required... Your father simply didn't care, or didn't know any better.
No, that's the whole point: the equipment was not required because there was no air pollution problem to begin with. We were saddled with a lot of superfluous emissions hardware in Oklahoma because it was needed in California.
The point of my CSB is that you can't possibly use your own preferences or localized requirements to gauge what's coming, or argue against it. Not in the car business, anyway.
You won't be putting a subway system into Dallas, it would cost a hundred billion dollars and still be poorly used, the city is too spread out. As it stands, we already have a multi-billion dollar light rail system that is poorly used and doesn't even run to half the city. The bus system costs just as much and is also poorly used...
What does any of this have to do with the subject under discussion?
A lot of people have ideas that might work in 2 or 3 big cities, but for the vast majority of America, have no chance.
I'm reminded of the emissions-control laws of the early 1970s, in that respect. During that time, I grew up in a flyover state in the middle of nowhere. There was widespread resentment -- more like frothing-at-the-mouth fury -- that our vehicles had to have catalytic converters, smog pumps, and endless tangles of seemingly-unnecessary plumbing under the hood, when there was clearly no problem with air pollution within a thousand miles or more. My old man constantly ranted about how the government was destroying the automobile industry out of sheer bureaucratic stupidity. There was an underground cottage industry devoted to bypassing and removing emissions equipment.
Now, 40 years later, I can go down to my local Chevy dealer and buy a 460 HP Corvette that gets 30 MPG. Oops. Guess my old man was wrong.
The same thing's going to happen this time, down to the last chapter and verse. People like you and me will scream bloody murder, and then we will wake up one day and realize we were wrong.
But not for me... Pride of ownership is a key point, having a nice well maintained vehicle that I worked hard for...
For the record, I'm with you 100% on that. I'm not personally going to like what I'm predicting, but I have no illusions that it won't happen exactly that way, because it makes too much sense in the vast majority of use cases.
Plus, my vehicle needs don't match most people's, I have a 7 person full sized SUV (Yukon XL) so I can haul the kids + stuff. JohnnyCab can't handle that.
Why not? There will be different levels of service, and numerous models of vehicles available at varying prices.
The rest of the objections people are raising go away when all of the autonomous cars are talking to each other and behaving as cooperative actors. On expressways, it will be only slightly more dangerous for a pack of "JohnnyCabs" to travel 10 feet apart at 100 MPH than it is for them to obey the current traffic laws designed for human judgment and reaction times. And on surface streets, traffic controls at intersections will be orders of magnitude more efficient.
Self-driving cars are mass transit. At some point, once you're no longer driving your car, it will occur to you that you don't really care if you own the car. That's when things will get interesting.
IMHO, most self-driving cars will be operated by a networked JohnnyCab-like service that will combine the efficiency of public transportation and the freedom of personally-owned vehicles. It will be a big social, political, and economic change, but almost everyone will end up better off.
The lag isn't just 30hz touch/refresh and triple-buffering. I've got a Samsung S3 and it feels like most actions take from around a second and up to complete
iOS is exactly the same way these days. Touch the screen. Nothing happens. Touch it again. Nothing happens. Touch it again, harder this time, and a bunch of stuff you didn't expect happens because the phone thinks you submitted three touches in a row.
This is one of my favorite responses to people who question the money spent on projects like RHIC and LHC. "You're right, there is no known application for this stuff. But aren't you glad nobody listened to your old man when he said the same thing about the laser?"
Slashdot Mirror
"No longer available in the US," according to the page you linked to.
I will say that's a really cool-looking spacey X-ray phaser gun, though. Tres Marvin the Martian.
Says the guy with his own 4 GHz computer, without the slightest trace of irony.
That's like saying to a software developer that he/she doesn't need to understand what memory leaks and segfault exceptions are, and how to prevent/fix them, because it's the job of the compiler to compile code in a way such that software never crashes.
And in a sandboxed, garbage-collected language, that would be exactly correct.
It's time for HDL developers to hold their tool vendors to the same standards that software developers expect.
But if you can't draw a K-map and cover glitch cases, just as one example, then you are not qualified to develop programmable logic.
Of course you are. That's what the tools are for. Nobody writing HDL needs to mess with Karnaugh maps, and once the tools get a bit smarter, they won't have to worry about domain-crossing glitches either.
*Wow, who is making the argument that we should "sacrifice free speech for a better society"? That sounds positively Orwellian. Or something from China, where the government runs a massive censorship operation.*
Read the comments in the NYT article. There are hundreds of them demanding just that. It's the scariest thing I've read in quite some time.
That's not a typo mistake. Sure enough, you are not intelligent as you think you are.
Not being very smart, I'll have to leave this word salad up to others to parse.
This gives me an idea, though. Perhaps the dumbshit programmers at Apple and Google should offer separate modes for their mobile operating systems: beginner, normal, and advanced. Copious text bubbles and prompts to explain and confirm various actions in beginner mode, some swipe actions disabled. Normal mode is similar to what is delivered now. And an advanced mode with more swipe actions akin to how keyboard shortcuts are used in desktop applications.
The "send my voice" feature is an example of something that should not be enabled by default, given the half-assed way it's implemented. Unfortunately, the centralized Settings menu tree is another weak point of modern iOS versions. Bury it in Settings and it might as well be lost forever. IMHO it's time to start associating Settings / Options buttons with individual applications again.
I'd probably put the "send my voice" button on an alternate keyboard or otherwise hide it. It's not a first-rank feature, and it shouldn't be in a position to be easily activated by mistake.
Sounds plausible, I'll bet you're right.
(Shrug) It wouldn't be unreasonable to ask my permission before transmitting an audio recording that I didn't even know was being made.
It happened. I don't blame you, I didn't believe it either.
Of course I knew the mic button existed, I use it all the time to dictate text messages. And I sometimes hit it accidentally, being a klutz. But in past versions of iOS, it's always been sufficient to hit 'Done' to make the mic UI go away. It has never decided on its own that, since it didn't recognize any valid speech, I must have wanted to record and attach an audio clip.
Sure, it's a nifty feature, as far as features go, but the failings are obvious: it should have asked me to confirm the attachment, or at least given me some indication that an attachment was being created. To the best of my recollection, there was no indication of that until after it was too late to remove the waveform attachment. (I'd say there's a 5% chance I'm wrong about that, as I wasn't paying that much attention.)
If anything in the message text is capable of crashing the app, the debate about who the dumbshit(s) are has already been adequately settled.
The other day I discovered a new iOS feature I had no idea existed. While sending a text to a customer, I hit the microphone icon by mistake. Another person in the (parked, idling) car was muttering about how the customer was a moron, which, although true enough, wasn't something I intended to include as part of the text. Not hard to see where this story is going, right? Well, it's even dumber than you're thinking.
I hit the 'Done' button to make the voice input UI go away, finished the text message, and hit 'Send.' As far as I knew, there was no danger that my friend's comment would be added to the text message. The car was too noisy and her voice was too low.for the speech recognition engine to understand, and in any event, the "moron" comment didn't appear in the outgoing text message. No problem.
Except what did appear in the text message, visible only after I sent it, was a small attachment balloon with a waveform. Apparently, iOS now sends the captured audio file as a binary attachment if it can't extract any recognizable speech.
So the obvious question is, what kind of drugs are these people taking? Is no one at a Fortune 500 company capable of thinking anything through these days? Do the programmers who think these features are "cool": and "awesome" not have managers with a three-digit IQ?
Fortunately for me, my phone lost its signal right about then, and I was able to kill the text app while it was still displaying "Sending." I knew from experience that iOS's text app didn't attempt to provide guaranteed delivery, and sure enough, when I restarted it, it had forgotten all about the message it was trying to send. So in a sense, I was saved by the same dumbshit programmers at Apple who tried to ruin my day.
It seems we have to adopt the same attitude around microphones that we normally apply to firearms. The gun is always loaded, and the mike is always live.
(Right rant, wrong target -- I was thinking of LightSquared.)
Lightspeed was terribly careless when it came to dealing with regulation
Yeah, they should have hired at least one attorney or at least one engineer who could tell the MBAs, "No, we can't use internationally-allocated satellite-to-ground spectrum for terrestrial communications."
But it's a lot easier to blame the big bad gubbermint.
Even if it is a self-driving car, a seat that 100 other people have sat in recently is still gross, and you can't ever clean it properly without replacing the seats often.
So I take it you don't fly?
But nobody would have cared if California had Oklahoma's population density. No harm would have been observed, certainly not at a scale that would prompt the creation of the Clean Air Act and a cabinet-level agency to enforce it. Mother Nature can absorb a certain amount of pollution of any kind... just not at California scale.
There are probably more cars in Los Angeles County alone (population 10 million) than in the entire state of Oklahoma (population 4 million).
*If it were just a local issue, then we could put 100 coal power plants in the middle of nowhere and it wouldn't matter. But ultimately they reduce the air quality everywhere over time.*
Quantity has a quality all its own. 100 coal plants is not a major problem for anyone not living next to one of them. 100,000 is everybody's problem.
Even in the 70s, someone who was educated and understood the problem knew that equipment was required... Your father simply didn't care, or didn't know any better.
No, that's the whole point: the equipment was not required because there was no air pollution problem to begin with. We were saddled with a lot of superfluous emissions hardware in Oklahoma because it was needed in California.
The point of my CSB is that you can't possibly use your own preferences or localized requirements to gauge what's coming, or argue against it. Not in the car business, anyway.
You won't be putting a subway system into Dallas, it would cost a hundred billion dollars and still be poorly used, the city is too spread out. As it stands, we already have a multi-billion dollar light rail system that is poorly used and doesn't even run to half the city. The bus system costs just as much and is also poorly used...
What does any of this have to do with the subject under discussion?
A lot of people have ideas that might work in 2 or 3 big cities, but for the vast majority of America, have no chance.
I'm reminded of the emissions-control laws of the early 1970s, in that respect. During that time, I grew up in a flyover state in the middle of nowhere. There was widespread resentment -- more like frothing-at-the-mouth fury -- that our vehicles had to have catalytic converters, smog pumps, and endless tangles of seemingly-unnecessary plumbing under the hood, when there was clearly no problem with air pollution within a thousand miles or more. My old man constantly ranted about how the government was destroying the automobile industry out of sheer bureaucratic stupidity. There was an underground cottage industry devoted to bypassing and removing emissions equipment.
Now, 40 years later, I can go down to my local Chevy dealer and buy a 460 HP Corvette that gets 30 MPG. Oops. Guess my old man was wrong.
The same thing's going to happen this time, down to the last chapter and verse. People like you and me will scream bloody murder, and then we will wake up one day and realize we were wrong.
Also, no wireless, less space than a Nomad.
But not for me... Pride of ownership is a key point, having a nice well maintained vehicle that I worked hard for...
For the record, I'm with you 100% on that. I'm not personally going to like what I'm predicting, but I have no illusions that it won't happen exactly that way, because it makes too much sense in the vast majority of use cases.
Plus, my vehicle needs don't match most people's, I have a 7 person full sized SUV (Yukon XL) so I can haul the kids + stuff. JohnnyCab can't handle that.
Why not? There will be different levels of service, and numerous models of vehicles available at varying prices.
The rest of the objections people are raising go away when all of the autonomous cars are talking to each other and behaving as cooperative actors. On expressways, it will be only slightly more dangerous for a pack of "JohnnyCabs" to travel 10 feet apart at 100 MPH than it is for them to obey the current traffic laws designed for human judgment and reaction times. And on surface streets, traffic controls at intersections will be orders of magnitude more efficient.
Self-driving cars are mass transit. At some point, once you're no longer driving your car, it will occur to you that you don't really care if you own the car. That's when things will get interesting.
IMHO, most self-driving cars will be operated by a networked JohnnyCab-like service that will combine the efficiency of public transportation and the freedom of personally-owned vehicles. It will be a big social, political, and economic change, but almost everyone will end up better off.
Wait until the next J. Edgar Hoover comes along. With the power of the modern security state behind him, he will seem more like Lavrenti Beria.
The lag isn't just 30hz touch/refresh and triple-buffering. I've got a Samsung S3 and it feels like most actions take from around a second and up to complete
iOS is exactly the same way these days. Touch the screen. Nothing happens. Touch it again. Nothing happens. Touch it again, harder this time, and a bunch of stuff you didn't expect happens because the phone thinks you submitted three touches in a row.
I don't think it's valid to use a couple of minor, specific, and temporary technical issues to condemn an entire trend.
This is one of my favorite responses to people who question the money spent on projects like RHIC and LHC. "You're right, there is no known application for this stuff. But aren't you glad nobody listened to your old man when he said the same thing about the laser?"