Have you even used a computer or any digital technology lately? Everything is slap full of lag now.
This demonstrates a complete lack of understanding of how a computer works. It also tells me you’ve never had to use any “old” computers for anything.
Sure, once modern chips gather all the data, they are pretty fast to process, but the lag time before the processing starts becomes significant.
The car’s computer starts when you turn it on… Not when a sensor is triggered. Do you seriously think the car’s hardware is booting up an OS or application every time a sensor event happens?
Yes, if you intend to swerve to try to avoid accidents, you’re going to want a camera. The first thing a cop is going to do is see that there are no skids where you should have been braking, and determine that you acted too late to prevent an accident. You’d be 50% at fault at best (assuming the other driver doesn’t admit fault). Consider that you could have lost control and hit another car, you could have hit someone coming up behind and passing you, you could have hit someone coming out from the other side who checked and confirm their direction of travel was clear… You got damn lucky, even if you won’t admit it.
Did you look at my username? Yeah, I’ve had that username before Google even existed. And for good reason too, timing things has been my game for more than half of my life.
I’ve written hardware drivers as small as 65 bytes. These days, hardware drivers are more like 65 megabytes, and that’s being very generous on the estimate, many drivers are way bigger than that.
Now, which sort of driver do you think can perform in realtime? 65 bytes or 65 megabytes?
Again, the more technology you throw at anything, the more lag it’s gonna have.
I’m all about safety and all, but when the operating system itself gets so complex and fragmented that it can’t even record the dashcam (looking at Tesla again), maybe it’s time to try to optimize and simplify things.
Yes, it actually is (at least partly) a driver bloat issue.
Seriously, go use a computer from like 1995, the mouse cursor works in realtime. Now use a computer today, the mouse cursor has a little light lag, just barely enough to really notice, but the lag is there. Half of that lag I chalk up to the video/GPU driver stack, but still…
Also, PS/2 vs USB?
Yeah, USB has limits on N-Key Rollover. What’s that mean? You can’t simultaneously press any more than 4 keys on a USB keyboard before the computer glitches out and gets confused, yet high quality PS/2 keyboards can recognize upwards of 9 (possibly even more) distinct keys being pressed at the same time.
I was talking more about the priority level of my USB vs PS/2. Not sure why you brought in limitations about simultaneous keystrokes, which has almost as little to do with what I said as this whole conversation has to do with a computer’s reaction time compared to a humans.
Let’s put it in perspective.
Average human reaction time is 250ms. The world record human reaction time is a blistering 100ms.
The Commodore 64 had a 1mhz processors. In the time it takes the average person to react, that machine can run
250,000 instructions, or 100,000 against the world record human reaction time.
Humans aren’t even close to computers in terms of sheer speed, and we haven’t been for nearly 50 years.
Also, while I don’t do flatland BMX or Unicycling, I am an avid gamer and a fire juggler. I think I know a bit about human reaction time… Unless you can demonstrate a human reacting faster than a computer can, then I’m not going to believe any off-side irrelevant weak-anecdotal point you’re going to make.
Congrats, interesting choice of sport/hobby, I hear ya.
That still doesn’t change the fact that the huge driver and software stack these days causes basic simple things like the mouse cursor to lag when same said hardware did not lag 30 years ago.
This demonstrates a complete lack of understanding of how a computer works. It also tells me you’ve never had to use any “old” computers for anything.
The car’s computer starts when you turn it on… Not when a sensor is triggered. Do you seriously think the car’s hardware is booting up an OS or application every time a sensor event happens?
Yes, if you intend to swerve to try to avoid accidents, you’re going to want a camera. The first thing a cop is going to do is see that there are no skids where you should have been braking, and determine that you acted too late to prevent an accident. You’d be 50% at fault at best (assuming the other driver doesn’t admit fault). Consider that you could have lost control and hit another car, you could have hit someone coming up behind and passing you, you could have hit someone coming out from the other side who checked and confirm their direction of travel was clear… You got damn lucky, even if you won’t admit it.
Did you look at my username? Yeah, I’ve had that username before Google even existed. And for good reason too, timing things has been my game for more than half of my life.
I’ve written hardware drivers as small as 65 bytes. These days, hardware drivers are more like 65 megabytes, and that’s being very generous on the estimate, many drivers are way bigger than that.
Now, which sort of driver do you think can perform in realtime? 65 bytes or 65 megabytes?
Again, the more technology you throw at anything, the more lag it’s gonna have.
I’m all about safety and all, but when the operating system itself gets so complex and fragmented that it can’t even record the dashcam (looking at Tesla again), maybe it’s time to try to optimize and simplify things.
Pressing X to doubt.
Also, in your other post, you’re glossing over PS/2 vs USB, and the priority level. It’s not really a software or driver bloat issue.
Yes, it actually is (at least partly) a driver bloat issue.
Seriously, go use a computer from like 1995, the mouse cursor works in realtime. Now use a computer today, the mouse cursor has a little light lag, just barely enough to really notice, but the lag is there. Half of that lag I chalk up to the video/GPU driver stack, but still…
Also, PS/2 vs USB?
Yeah, USB has limits on N-Key Rollover. What’s that mean? You can’t simultaneously press any more than 4 keys on a USB keyboard before the computer glitches out and gets confused, yet high quality PS/2 keyboards can recognize upwards of 9 (possibly even more) distinct keys being pressed at the same time.
I was talking more about the priority level of my USB vs PS/2. Not sure why you brought in limitations about simultaneous keystrokes, which has almost as little to do with what I said as this whole conversation has to do with a computer’s reaction time compared to a humans.
Let’s put it in perspective.
Average human reaction time is 250ms. The world record human reaction time is a blistering 100ms.
The Commodore 64 had a 1mhz processors. In the time it takes the average person to react, that machine can run 250,000 instructions, or 100,000 against the world record human reaction time.
Humans aren’t even close to computers in terms of sheer speed, and we haven’t been for nearly 50 years.
You don’t ride BMX flatland or unicycles do ya?
https://youtube.com/watch?v=QM1rCkjaiCY
In BMX, you don’t even get 10ms to think. I drive vehicles with the same level of quickness and awareness.
I literally don’t care.
Also, while I don’t do flatland BMX or Unicycling, I am an avid gamer and a fire juggler. I think I know a bit about human reaction time… Unless you can demonstrate a human reacting faster than a computer can, then I’m not going to believe any off-side irrelevant weak-anecdotal point you’re going to make.
Congrats, interesting choice of sport/hobby, I hear ya.
That still doesn’t change the fact that the huge driver and software stack these days causes basic simple things like the mouse cursor to lag when same said hardware did not lag 30 years ago.
Literally doesn’t matter. Automatic braking systems aren’t moving a cursor around and clicking on the “Brake” button.