I'm not the OP, and I don't know about Polestar specifically, but I've worked with many other vehicle systems, and they are incredibly complex. Each ECU in a car is running it's own firmware, and the larger ones can be running their own OS.

There's usually a mix of Assembly, Simulink, C, C++, Java, JavaScript, Shell scripts, Python, etc...

I've seen the OS be various flavors of embedded Linux, QNX, or even Ubuntu.

You can usually find a bit of everything even in a single vehicle. The code is integrated by an OEM and can come from dozens of potential suppliers.

I side with you. Basically "Volvo is using Rust..." translates to: "Volvo is adding Rust to its stack of complexity".

This comment makes me want to use a bicycle from now on.

I've seen rust used in a lot of bicycles.

More seriously, most ebike firmware is written in C.

My bikes run c++ (both arduino and segger-flavored) and a funny language called monkey-C in the subset of the code I know. And presumably mostly c++ in the parts that I don't know (much larger parts). Some people I ride with also have java in the mix and it doesn't seem to bother them at all.

Just use a 90s EFI vehicle with a full modern aftermarket ECU system from Haltec or Motec or whomever, and you can have a better car than was ever sold OEM.

There's no mention of the Rust language on the site or their careers page, at least with queries like `rust site:www.polestar.com/us/` or `rust site:about.polestar.com/careers/jobs/`.

Keep in mind that 90% of the engineering done in a car comes from a supplier or the supplier of supplier

Don't know for sure, but their share the "platform" with Volvo.

That's off the point though. The choice of language matters, but it matters less than the development process and the professionalism of people involved.

From what I can tell from test driving a Volvo CX90 and a Polestar these cars don’t have much in common in terms of software.