Today’s “FSD” has its limitations and requires supervision, but your description of it is not anything like my experience even on a HW3 vehicle. In fact, in many years of using Autopilot and various “FSD Beta” and “FSD (Supervised)” versions for several tens of thousands of miles I’ve literally never seen it “slam on the brakes suddenly for shadows” or “veer into the wrong lane”. I’m not a cult member and my next car won’t be a Tesla because I cannot support Musk after the horrible things he has done these last 2-3 years, but “FSD” is phenomenal when used appropriately and with the right expectations about what it is and what it isn’t. And it has improved a ton over the years, too.
The end-to-end solution was a real game changer, and while the previous solution was still useful and impressive in its own right, moving to the new stack was a night and day difference. With V13 finally taking advantage of HW4, and all the work they’ve been doing since then (plus upcoming HW5 introduction), it’s totally within the realm of possibility that they achieve viable L4 autonomy beyond this kind of small scale demo (and I hope some form of L3 maybe on HW4 before long for customer vehicles).
They collect video, not images, along with other sensor and control data.
It’s not a sunk cost fallacy, it’s a technical strategy that is very logical and showing compelling results (though as of yet unproven for achieving robust L3 or L4 autonomy, demos notwithstanding).
Driving over a double yellow is expected and legal in normal driving, such as when making a left turn or going around an obstruction.
In this example it looks like it oscillated between two different routing choices (turning left and going straight), and by the time it decided the correct route was to go straight, it found itself misaligned with the lane it should have been in. Instead of moving all the way back to the right, it kind of “cheats” its way into the upcoming left turn lane. This isn’t something it should do in this situation, but it’s likely emulating human behavior seen in situations like this which appeared in its training data, where people cut across the center line(s) ahead of the turn lane forming when they can see that it is clear.
The thing a lot of people get wrong is that they think the most valuable data for Tesla to collect are the mistakes or interventions. Really what they need the most is a lot of examples of drivers doing good job of handling complex situations. One challenge, though, is separating out those good examples from the less good or bad ones, as human drivers are notoriously bad at, well, driving.
They used it on test mules to create labeled training data for their older monocular depth / Occupancy Network models (which they still use as part of the supervisory policy enforcement and active safety layer, alongside the end-to-end model).
They’ve never had LiDAR in their cars and it would not ever have been practical for them to have done so. Nobody has any mid or long range LiDAR in vehicles as the scale that Tesla sells.
In a perfect world, AV software wouldn’t be necessary. We don’t live in a perfect world. So we need defense-in-depth, covering prevention, mitigation, and remediation.
How is it meaningfully different with respect to this question?
If I go to a museum and look at a bunch of modern paintings, then go home and paint something new but “in the style of”, this is well-established as within my rights, regardless of how any of the painters whose work I studied and was inspired by might feel.
If I take a notebook and write down some notes about the themes and stylistic attributes of what I see, then go home and paint something in the same style, that too is fine - right? Or would you argue the notes I took are a copyright violation? Or the works I made using those notes?
Now let’s say I automate the process of recording those notes. Does that change the fundamentals of what is happening, with respect to copyright?
You might consider that your needs are not representative of the overall Windows population. For example, one reason some of these key combinations are important is for accessibility.
This is not an accurate way to measure the size of Windows as most of those folders contain no files, just hard links. There is no reason for you to have to worry about deleting "defunct system files", the OS handles this just fine on its own.
You do not have to set your connection to metered to disable P2P updates, there's a setting just for that, and there's really no reason to disable it in the first place.
Reboots are usually required for monthly "patch Tuesday" updates, though sometimes they are not. Out-of-band updates are rare but do happen in the event of a critical, urgent security update.
The OS only sets a deadline for the reboot (where it will force if you postpone too long) if the update includes a critical security update.
Firmware and core driver updates also require a reboot, but don't have deadlines and the schedule depends on the hardware vendor.
Oh, and if your machine is in the Windows Insider program, all build upgrades have deadlines so you hit the "forced reboot" much more often than a normal user.
This is incorrect. The programmed pinned apps in the current releases of Win10 are only applied to new installs or when upgrading from Win7 or 8.x. They are never applied during Win10 updates (unless there's a bug of course). The entire pinned space is customizable by the user and user customizations are always maintained.
Putting a couple ads in free games in the App Store is not "screwing over people". Nor is it "anti-consumer".
In fact, the whole point isn't even to make money from them, but to support the Windows developer ecosystem by promoting other apps and jump starting a viable ad network.
Also note that Apple and Google do the same thing.
This is in fact untrue. You would not have needed a new license for a replacement motherboard if that really happened. At worst you might need to make a phone call to MS, though even that is an unusual case.
The end-to-end solution was a real game changer, and while the previous solution was still useful and impressive in its own right, moving to the new stack was a night and day difference. With V13 finally taking advantage of HW4, and all the work they’ve been doing since then (plus upcoming HW5 introduction), it’s totally within the realm of possibility that they achieve viable L4 autonomy beyond this kind of small scale demo (and I hope some form of L3 maybe on HW4 before long for customer vehicles).