That means 600km becomes 400km or less at 80% charges, and when you drove 140km/hr or more, the acceptable speed in many US states, that means less than 3hrs, and 600km isn't rated at 140km/hr speeds!
In other words, EVs don't work for long range driving.
Some may drive slow, or not count the 10 minutes to get on/off road and find a charger, and the 20 minutes to hook up and charge, and the potential to not find a free charger.. but I did.
And when I used these sensible, real world values, a trip from Quebec to California, which I take from time to time, changed from 3 days, to 8.
Lots of people drive like this. Lots. Especially Canucks wanting to escape snow, darkness, and wolves.
I've seen all the replies before, and all of them take some random thing, which I base on reality, averages, and fact, and try to pretend that ot doesn't matter.
But it does.
As others have said, if you are city driving only? Great! And many families have two cars, and that's another great place for an EV. One EV, on gas.
And we will get there range wise. We're just not even close yet, for long drives.
The complexity comes in with the ecosystem and nix-the-build-system, each of which has a dozen different ways to do any given thing, all of which are in active use simultaneously. Some are pretty baffling, like nixpkgs' dual role as both the main package repository and the (almost entirely undocumented) de facto standard library
Nixpkgs specifically needs to be entirely rethought. It has become too large and complex to manage both technically and politically with the number of contributors. Separating out the lib, stdenv/tooling, and package definitions would be a good start.