Brakes need to be inspected but my last ICE vehicle went about 90k miles between needing pads. My EV has sealed drums in back (a choice VW made to reduce friction when brakes aren't in use and I think trying to slow corrosion of the components) and conventional large discs in front. If we have issues with the front brakes it will be due to corrosion as I don't expect to put enough wear on them to ever wear through the pads. In normal driving the brakes are only applied at full stops.

I don't expect EVs to have motor mounts like an ICE vehicle, as the motor is a few orders of magnitude smoother (commutation ripple vs cylinder firings) and shouldn't need fluid-filled rubber isolation mounts.

If I think of what I've had to replace on my cars over the years, half-shafts and CV joints and wheel bearings might now be the least reliable mechanical things on the car, plus the oddball failures, like a clock spring in the steering wheel or a window motor.

So I still have to keep tires inflated, rotated and balanced, keep good wipers installed, change the cabin air filter occasionally, and listen to the rest.

My source for my opinion is having done the vast majority of the maintenance and repair of our cars over roughly 4 decades and more than a million miles.

I will agree that a temperature interface in °C should read in increments of 0.5 in order to have roughly the same resolution as when in °C (and many don't, but that's poor UX). I don't care about 0-100 being roughly aligned to human environments - 0-100 being aligned to freezing/boiling of water is just as good a reference.

[1] of the many things that Reagan should be despised for, cancelling metrication is probably not in the top 5, maybe not top 10. I still despise him for it.

I started using python for various engineering analysis problems around 2001 and I loved it for how fast (due to minimal boilerplate and automatic memory management) I could code up some thought relative to using C or Java. I could tackle problems in ways I just wouldn't have tried otherwise because I couldn't afford the longer time to write it in other languages. However, for problems which needed speed, of course it bogged down.

I started using Julia for ODE stuff in 2018 or 2019 and was thrilled with the speed and conciseness. As others have said, it looks much more like math and a lot of better design choices were made.

Python obviously has a much larger ecosystem and probably always will, and it will remain a safe choice, but you don't set yourself apart by doing the same thing as everyone else.

A Dornier 328 (roughly similar in size) has two 1625 kW engines. Heart stated they "delivered more than one megawatt of power" during the flight, so maybe comparable to one of the Dornier's engines at 60% power? Even the DC-3 could take off with one engine but 60% seems iffy.

At 1000 kW and $0.10/kWh (being very generous I think), the plane would be using $100/h (at 1000 kW level) or $1.67/minute. You'd blow past $5 in 3 minutes.

I don't like that they don't share the basic numbers. It's as if they don't want folks doing the math.