You should be able to recharge at least 200 km of range in a 20 minute stop which is probably enough until your next break. An ICE lets you cut out those breaks but you really shouldn't because breaks are good for you (and your driving).

Either your car or whatever you use for GPS directions already handles the planning for you. It will automatically find and route you to chargers as needed.

Didn't mean it in that way. I meant a car with camera+lidar would realistically still slow down because of the reduced camera visibility.

> Tesla stans are the only ones trying to convince everyone you can only drive with cameras. Everyone else is pretty united on the usefulness of multiple inputs.

Ignore them. The latest Model S and X have radar again, but possibly unused right now, so they are probably going to roll that out in a refresh of the 3 and Y eventually.

The real answer is very simple: safe drivers slow down to adapt to poor conditions (including visibility). Lidar might reduce how much it needs to slow down but I don't think it will be eliminated because you can't drive with only lidar.

But my point is that the reference to the function you are calling is actually its own term that needs to be considered in the order of evaluation.

You can also use the IIFE (immediately invoked function expression) pattern that is/was common in JS as an example:

  (function() {
    // ...
  })();

  foo.bar(x)

  foo()(bar())

Memory use alone is an interesting case for comparison because websites tend to have a lot more images/videos loaded than other applications. All of those PNGs and JPEGs need to be decompressed before you can paint them to the screen which makes them much larger.