News for hackers. Stuff that matters.

alesso_x

> The self-driving subject vehicle is a 2020 Tesla Model 3. The Tesla fatally struck a motorcyclist from behind at above 100MPH on a 45MPH speed limit road

FSD cannot be turned on above 85 mph. If you try to accelerate above 85 mph it disengages.

> That’s how you would strike a motorcyclist at such extreme speed, simply press the accelerator and all other inputs are apparently overridden.

If the user is pressing the accelerator pedal, it overrides the autopilot. I’m not sure how FSD could reasonably be blamed in that situation.

The article also talks about Traffic Aware Cruise Control (TACC). There is a nuance between the different systems. This is not Full Self-Driving (FSD). It is an older system that Tesla provides for free. All it does is try to maintain a set speed, and you still have to steer. If the user is pressing the accelerator pedal, it overrides the system. I am not sure how FSD could reasonably be blamed in that situation.

It’s a completely different system. Comparing it to the old one is like comparing apples to oranges. The original highway stack didn’t feel natural at all. It was like every move was hard-coded.

Lane changes used to feel robotic. Speed had to be adjusted manually all the time just to feel comfortable.

The new system feels much more human. It has driving profiles and adapts based on traffic, which makes the experience way smoother.

Have you tried fsd? I use it almost everyday in the chaotic streets of NY. I’m more arguing that the article is misleading about the current version of fsd. I do not doubt that the accidents happened on the older version.

The article gives a pretty misleading impression of where FSD stands today. It treats highway behavior as if nothing has changed, but that’s not accurate.

Before October 2024, the highway stack was still running on Tesla’s older software. A major shift happened with version 12.5.6, which brought the end-to-end neural network to highways for the first time.

Then in December, version 13.2.2 pushed things even further by scaling the model specifically for HW4/AI4. It’s a major step up from earlier versions like 12.3.x from April.

I absolutely feel for anyone who’s been involved in an accident while using FSD. But at the end of the day, the system still requires driver supervision. It’s not autonomous, and the responsibility ultimately falls on the person behind the wheel.

If you’re going to evaluate how FSD performs today, you really need to be looking at version 13 or greater. Anything older just doesn’t reflect what the system is capable of now.

Re:How to stop turmeric from killing people on Saturday November 04, 2023 @09:35AM (#38140861)
I have to turn off apple private relay to avoid the recaptcha loop.
Re:Text editing on mobile isn’t ok on Sunday September 24, 2023 @10:49AM (#37633651)
Long press on space bar to move the cursor is great. Also iOS supports “Drag Press for text selection” which the article says it has implemented.
Re:Apple ExtensionKit on Monday October 31, 2022 @02:18PM (#33410135)
I wish Apple docs would include examples. I'm not an Apple developer but I've played around with SwiftUI and they have fantastic examples.
Re:Celery in production: Three more years of fixing bugs on Saturday March 05, 2022 @10:54PM (#30574895)
I totally agree, I would not recommend using Celery. The last time I used Celery was in 2019 and it was a mess. The memory leak issue is still open https://github.com/celery/celery/issues/4843 to this day.
Re:Node.js Notebooks on Sunday February 20, 2022 @07:05PM (#30410494)
I'm a huge fan of Don Jayamanne. He also made the original python extension for vscode.

I always wondered why no one made a better node.js repl. I wish there was something like ipython for nodejs.

Re:Real-world CSS vs. CSS-in-JS performance comparison on Tuesday June 08, 2021 @05:18PM (#27440970)
The website is being rate limited, here’s a google cached version

https://webcache.googleusercontent.com/search?q=cache%3Ahttp...