Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> I am aware that FSD has a different software stack. But it's the same hardware. So why would they make the detection of kids different on the standard firmware artificially worse? As Marketing for people who hate school kids?

Not sure what's your argument here. The visualization you get using "Enhanced Autopilot" is completely different to the one you get using "FSD Beta" because the software you are running is completely different as well.



The point is not the visualization towards the driver. It's that the same data clearly is the base for the decisions this car makes. If it is not showing the kid crossing the street, you also will not get an emergency break warning, which I get in tons of other situations.

What you see is what you get.


I'm sorry, I struggle to understand your point. Which one is it?

- Do you think that a Tesla with an enhanced Autopilot would hit a kid because you don't see it in the visualization?

- Or do you think that a Tesla with FSD Beta would hit a kid because it uses "the same data" as the one without it?


I think the idea is, why would the visualization be so intentionally bad in the Autopilot version as to not detect the kids entirely? What benefit does that confer, or, from another perspective, what software constraint forces this to be the case?


It's not _intentionally bad_. Autopilot and FSD are _different products_ with _different tech_.

It's not like they could simply copy `detect_children()` from FSD to Autopilot and call it a day.


Hmm, that might be possible, but that's essentially not what I assumed. At the very least, they operate on the same hardware, so Autopilot is in some sense "intentionally bad" as a whole.


Exactly that, yes. Thank you.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: