Sentau

I haven't hit a deer, not even come close since they aren't a problem in my country. You are most probably right and i have seen videos of deer just jumping onto the road at the last second which causes an unavoidable accident. My viewpoint is that when you hit a creature(animal or human) at 80mph, they are most certainly dead. If you hit them at 60, they might survive but be gravely wounded. If are able to react and slow down before contact to about 30, they will be hurt but at least they have a much better chance of the survival. Somehow going at same speeds during the day and during the night seems very risky

It was an expressway. There were no lights other than cars. You're not wrong, had a human sprinted at 20mph across the expressway in the dark, I'd have hit them, too. That being said, you're not supposed to swerve and I had less than a second to react from when I saw it. It was getting hit and there was nothing I could've done.

I am neither blaming you nor critiquing your actions. In fact I agree that we should not swerve. I was just making an observation that driving slightly slower in low visibility might help by giving you more time to notice an obstruction and brake while provide also providing more time for the obstruction to react and clear the road. At least very least, people might slow down enough so that the crash is no longer fatal to the person or animal being crashed into

Nobody is asking you to go at 35 mph. But going 60 mph instead of 80 mph means that your stopping distance will be nearly half and you will have almost twice the amount of time to react.

https://www.automotive-fleet.com/driver-care/239402/driver-care-know-your-stopping-distance

Maybe drive a little slower at night. If you can't spot and react to animals on your path, you won't able to react when it's a human

Well my comment was not about having control over the software/firmware though that will be cool.

My logic is that well tested, polished software/firmware have very few bugs and hence most of the updates they get are feature additions or improvements to current functionality (examples in an EV could be updates making the BMS more robust, tweaking the regen modes according to feedback from the users, etc). Poorly tested, half baked software/firmware will be full of bugs and broken functionality and will lead to 'updates' where all the changes are correcting broken functionality and serious bugs. This will be an unpleasant experience for the user and we should hold companies accountable when they do shit like this

Dude I think you have replied to the wrong comment

There is a difference between software getting updated and software getting fixed though. We want the first scenario not the second one

Wait what!?

They've got over $25B in cash reserves

What. I haven't heard about this massive reserve

if you have to wipe with toilet paper anyway, doesn't that defeat the purpose of having a bidet?

No. The purpose of the bidet is to properly clean your posterior which cannot be achieved with toilet paper alone. Also the amount of toilet paper needed to dry is lower than the amount needed to 'clean'

They are both describing the same particles.

Water and ice are made up the same particles and molecules yet the mathematical structure to define the effect of force/pressure is very different - plastic deformation vs fluid dynamics as the example given above

Neither of them is trying to model the universe (that is the purview of cosmology). We are trying to model very particular phenomenon happening in the universe and there is no reason to expect them to modeled using the mathematical structure. The fact that they are is very fascinating.