That’s exactly my thoughts. Code and documentation are one of the primary types of „content” by/for engineers. Kind of goes against the main topic of the article.
That's unlikely. Try driving in a snowstorm, where visual inputs become effectively useless, and you quickly realize how much the motion inputs are factored in as well.
They are very different problems. You can attach every kind of sensor to the phone and get HD images, lidar scan, 3D model, heat signature and whatever other signal you want, but you still won't be able to figure out calories in a piece of food without breaking it apart at a molecular level. There's just too much hidden information. What sensor will tell you how many tablespoons of oil the chef used to fry onions for the sauce? Heck the chef himself probably won't be able to tell you.
I legitimately drove full month with near zero interventions in FSD. The second statement is achievable in my opinion. Most people have not experienced hw4 with latest releases.
That's an interesting comment, but I have driven in heavy rain, and it worked just fine. Can you share how you arrived at your conclusion? I mean there is a limit to where the obstruction is so intense that even human cannot drive I get that but its actually performing fine for me in heavy rain that is still drivable for a human.
Every person being rescued must have the app.
Only one person rescuing needs to have the app.
It'll be easy to find a collapsed building site. The person rescuing just needs to be close to the site with the app. Otherwise, the signal might not be noticed.
+1 regarding finding survivors for malicious purposes. I tried my best to lower the surface area of that happening. It's still possible in edge cases, like opposing soldiers finding the people transmitting SOS, but they need to be extremely close to do that.
And no one is stopping anyone from tweaking few parameters in this repo to go above 10M parameters.