News
Opinion: Tesla FSD Beta critics’ pearl-clutching and outrage are getting ridiculous
Tesla’s “Request Full Self-Driving Beta” button is here, and so is the Fear Uncertainty and Doubt (FUD). Over the weekend, Tesla owners with qualified vehicles and who purchased the company’s Full Self-Drivings suite were able to press a button that would allow them to apply for a slot in the company’s soon-to-be-expanded FSD Beta program. The company also launched its Safety Score system as a way to help determine which of its customers are safe drivers.
True to form, it did not take long before Tesla critics pounced on the “Request FSD Beta” button and the company’s “Safety Score” system. Pretty soon, even a US Senator joined the fray in condemning the FSD Beta program. While this is not a surprise and almost expected considering Tesla’s history, it must be said that this time, the pearl-clutching and outrage from the company’s critics are getting quite ridiculous.
Tesla’s Strategy
To get proper context on the FSD Beta expansion, one must know how Tesla started the program in the first place. The FSD Beta program was launched in October 2020, and for nearly a year, it was limited to just about 2,000 drivers. These drivers have accumulated valuable real-world data over the past 11 months, and none were involved in an accident. This effectively did two things: one; it proved that the FSD Beta program is feasible, and two; it set a very high bar for the rest of the FSD Beta rollout.
Expanding the FSD Beta program requires tons of caution. Thus, it was no surprise that the company launched a Safety Rating system designed to evaluate the driving behavior of Tesla owners. This effectively gave the company a rather objective way to evaluate which drivers could participate in the FSD Beta program expansion. It should also be noted that owners who qualify for the program would not be using a consumer release version of the Full Self-Driving suite. They would simply be part of the FSD Beta test program.
Clutching Pearls
This fact seems to have escaped some of the media coverage about the FSD Beta program expansion. Bloomberg, for one, ran with a headline that read “Tesla Starts Judging Owners It Charged $10,000 for Self-Driving.” This premise is quite incorrect as the $10,000 Full Self Driving suite being sold by Tesla is a consumer release product, not the advanced driver-assist system that would be used by owners who qualify for the FSD Beta program. Despite this, sentiments opposing the program, as well as the Safety Score system, have been quite evident among the company’s critics.
Such a misinformed take was evident in a Twitter post shared by US Senator Richard Blumenthal, who noted that Tesla was “putting untrained drivers on public roads as testers for their misleadingly-named, unproven system.” The Senator added that the FSD Beta strategy is a “seeming recipe for disaster” as the company is playing “Russian Roulette for unsuspecting drivers & the public.” Interestingly enough, the politician also cited a tweet from CNBC, which included an article that is, in many ways, slanted against the EV maker.
Outdated Information
Wrong takes on hot topics are typically due to outdated information, and in the case of US Senator Blumenthal, this might be the case. Back in 2018, the politician rode in a Model 3 with Consumer Reports Head of Auto Testing Jake Fisher, who was operating a version of Tesla’s Autopilot that is now incredibly outdated. During the drive, Fisher was quick to point out what capabilities Autopilot was lacking, all while operating the system without his hands on the wheel.
Consumer Reports is hardly a Tesla authority considering that the magazine, which prides itself on consumer advocacy, quite literally featured a thorough walkthrough on how to abuse Tesla’s Autopilot system back in April using defeat devices and a variety of tricks. If Blumenthal is basing his take on Tesla on CNBC‘s recent reporting — which was slanted negatively against the EV maker — and his past experiences with Consumer Reports — which operates Autopilot irresponsibly — then it is no wonder that he is skeptical about the FSD Beta test expansion.
The Irony of it All
The most ironic thing about the pearl-clutching and outrage among Tesla critics today is the fact that the “Request FSD Beta” button essentially does nothing for now. It does not make owners who press the button automatic FSD Beta testers. They’d have to have great Safety Scores for that. And due to the presence of Safety Scores, Tesla owners who wish to participate in the FSD Beta program are now driving safer than ever before. The company effectively incentivized safe driving this weekend, and somehow, it was still met with a ton of negativity.
-
Also ironic is the fact that statistics are on Tesla’s side. Take the well-publicized NHTSA investigation on Autopilot crashing into stationary emergency vehicles, for example. When the probe was launched, the news was extensively covered with headlines like CNN‘s “Tesla is under investigation because its cars can’t stop hitting emergency vehicles.” But while such headlines are compelling, the fact is that the US Government Accountability Office (GAO) report notes that there are about 8,000 stationary emergency vehicle crash injuries per year. Tesla had nine crash injuries with stationary first responder vehicles in the last 12 months, and some of those involved drivers who were not paying attention to the road.
The NHTSA notes that there are about 2,740,000 crash injuries in the United States per year, and there’s hardly any outrage for the human lives included in this grim statistic. Tesla’s Full Self-Driving system, which generally drives very conservatively, could effectively reduce this number by a notable margin. It is then quite disappointing to see the narrative being formed around the expansion of the FSD Beta program, especially considering that the advanced driver-assist system would only be released for owners who generally drive safely.
Valid Tesla Criticism
Interestingly enough, there are actual valid angles of criticism for Tesla’s FSD Beta rollout. The program for now is vastly focused on the United States, but the company sells the FSD suite to owners worldwide. It would then be beneficial to Tesla owners if the program’s expansion is expedited to areas such as Canada and Europe, to name a few. FSD, after all, is intended to be a universal system that should be capable of operating anywhere. Following this logic, FSD Beta must be tested on a wider set of areas as well — as soon as possible.
There are also Tesla owners who purchased the Full Self-Driving suite years ago on vehicles that are still equipped with MCU1 units. Some of these vehicles are already coming out of warranty, and their owners are yet to enjoy any FSD features since most of the advanced driver-assist system’s functions today require an MCU2 unit. Considering that Tesla owners were promised that their cars would be equipped with the hardware necessary for Full Self-Driving with an FSD suite purchase, it would only be right for Tesla to expedite MCU1 to MCU2 retrofits for owners with vehicles that were produced from March 2018 or earlier.
But misrepresenting the FSD Beta program expansion and criticizing the Safety Score system, that’s a far harder sell.
Don’t hesitate to contact us with news tips. Just send a message to tips@teslarati.com to give us a heads up.
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
