• over_clox@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    8 days ago

    Yes. If you’re going the speed limit of 25mph on a service road, in broad daylight, and some idiot backs out in front of you when you’re only about 15 feet away from them, then there’s no way in hell that you’ll be able to stop the car in time.

    Dude had absolutely no excuse for that either, it was a perfectly clear line of sight, dude just didn’t look.

    Why don’t you try stopping a car going 25mph within 15 feet of distance? It’s not possible in such a short distance.

    It’s called inertia, look it up.

    • Bytemeister@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      8 days ago

      Ah, see, you’re making a straw man here. I did not say anything about being able to stop the vehicle in time.

      What I did say is that you swerved your car, without checking that the next lane over was clear.

      instead I jerked my steering wheel to the left

      And that you still had an accident.

      I just clipped his back bumper.

      Let me know if you need more clarification on what you wrote.

      • over_clox@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        8 days ago

        There wasn’t any vehicle in the other lane. There wasn’t even any other vehicle on that stretch of road.

        I knew what options I had, and there were only two.

        1. I could have slammed on brakes, but the car wouldn’t have stopped in time. Any attempt of braking on my end would have just given him more time to back out in front of me, which would have led to a side impact and major damages.

        2. I didn’t want to give him any more time to back out further, so I chose a different maneuver, to quickly steer left to avoid a full side impact. I avoided the brakes because I knew they would have actually made that particular exact situation worse.

        So I clipped his bumper, so what? No matter what I did, an impact was inevitable anyways, and it was totally his fault. I just made a really quick decision that avoided significant side impact damages.

        And yes, I made that decision within approximately 1/10th of a second. I don’t think a chip would have done that, a chip would have just attempted to stop, yet due to inertia, would have still slammed into the side of his car.

        • Bytemeister@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          8 days ago

          What I’m saying is, the computer can react faster than you can. This is not up for debate, it’s a fact, and it’s been a fact since the late 70s. Yes, when the car is in an impossible situation, it will get into an accident. Yes, you still need to drive the car. Yes, you mitigated an accident, but you did so at the risk of creating a much worse accident (collision at a high speed, potentially involving other cars in a crash) and implicating yourself as an at-fault party. You got lucky, you may not see it that way, but you did. Sure the other driver fucked up, no argument there. You know what would have helped them though? Cross traffic alert system, and automatic braking to stop them from backing into your lane, hell, it may have triggered on their vehicle and prevented your high(er) speed bumper scrape gambit from being a much worse accident.

          Also, it’s sounds like the real piece of safety equipment is you need is a dashcam.

          • over_clox@lemmy.world
            link
            fedilink
            arrow-up
            1
            ·
            8 days ago

            Regarding lag time, let’s compare and contrast older vs newer technology.

            Go back to the 1990’s and use a computer mouse. The cursor responds in realtime.

            Now compare to modern technology, that same mouse cursor has like a 10 to 20 millisecond or so lag. Hell, even the keyboard and game controllers these days have lag.

            So, you got way faster chips these days, but also a way overcomplicated stack of software causing the lag.

            Old technology used to be instantaneous and respond to the operator/user in realtime.

            These days the computer is bogged down by tracking everything you do, logging every single thing, communicating with servers to see if you were tugging your dude rope when the accident happened, etc…

            TL;DR - Believe it or not, simpler older technology would respond faster, because it was just you and the vehicle directly operating together, not having to communicate with some mass computer server farm to figure out what to do.

            Lag. It’s a thing. Ask any gamer how that fucks their games up. Driving a vehicle isn’t a game though, but apparently these days it’s still prone to lag, because there’s just a ridiculous amount of unnecessary technology ticking behind the scenes.

          • over_clox@lemmy.world
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            8 days ago

            Have you even used a computer or any digital technology lately? Everything is slap full of lag now.

            Sure, once modern chips gather all the data, they are pretty fast to process, but the lag time before the processing starts becomes significant.

            Yeah, a dash cam might have been nice, it sure would have shown much easier than me trying to explain what happened.

            • Bytemeister@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              8 days ago

              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.

              • over_clox@lemmy.world
                link
                fedilink
                arrow-up
                1
                ·
                8 days ago

                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.

                • Bytemeister@lemmy.world
                  link
                  fedilink
                  English
                  arrow-up
                  1
                  ·
                  8 days ago

                  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.

                  • over_clox@lemmy.world
                    link
                    fedilink
                    arrow-up
                    1
                    ·
                    8 days ago

                    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.