Very much not in the USA confirmed.
Okay, 50% of the battery is sort of true - though 60-70% can be standard. Charging doesn't typically slow because you've charged the battery 50% of it's capacity, it is because charging slows at around 80% total charge, depending on exact chemistry. IE it slows not after charging 50% in a single session, but upon reaching ~80% full.
10% to 80% is going to take longer than from 10% to 50%, but it will still be fast. It's just that that extra 30% isn't going to allow skipping the next charging station, so why bother?
As such, only needing 50% more charging sessions, is still possible. By math it'd actually be closer to 30%.
Now, if you look at an unladed truck with 500 miles range vs a 300 mile EV, that's where you start needing to stop a lot more often, but again, remember I'm advocating trucks be hybrids and cars going EV first.
How is China being micromanaged when there are now multiple independent starship competitors?
Because they aren't independent.
I don't get the Rust hatred. C has implicitly had an "unsafe" mode for much longer than Rust.
If you're a C kernel developer, you can jump on the Rust bandwagon very easily: just put the keyword unsafe in your comments and you can write code just like Rust developers.
Maybe, just maybe, this mistake was caused by the fact that the same sort of people who are likely to write bugs into their code are the same types of people who prefer "safe" languages because understanding the subtle nuances of how computers work is difficult. They would prefer a system where they couldn't make mistakes, rather than a system where they had to understand the code and the machine to a high level. There's a place in the world for these sorts of people, but it's not in OS/kernel development. The sort of I-can't-make-mistakes-with-Rust mindset probably lulled the coder into a false sense of security, with the predictable outcome.
Your mentioning having slow chargers at destinations, such as offices, is actually a potential solution to apartments being slow about installing charging capacity, or being too expensive about it.
Have people charge at work, not home, in such cases.
The workplace will probably want reasonable rates, many already cover parking for their employees, and with solar power ever expanding, daytime power might actually become cheaper than nighttime.
For areas with actual parking lots, imagine covering the lot with solar panels. Help keep cars cool and clean, not snow covered, etc... While charging them up.
Might not work as well in the extreme north, but not all of the USA is that far north.
I don't remember the last time I visited a gas station in the United States that didn't have pay at the pump available. I'm sure there are some janky stations out there, but not many.
Plus, at least in the USA, refueling one of our 300 mile ranged EVs is only maybe 50% more often than a gasoline vehicle - you don't want to go under 10% in a gasoline vehicle anyways, but while full is not a problem with ICE, with an EV you probably want to stick to around 80% most of the time to avoid the charging slowdown (upcoming tech may change this). 30% is probably closer. IE if you need to fill up 10 times with an ICE vehicle on a trip, with an EV it'd be 13 charging stops.
Plus or minus some accounting for placement of towns and charging/fuel stations.
That's only about 60 miles difference,
The reason people will roll their eyes at you over that is that its an incredibly boring debate that ended 30 years ago.
And yet, you jumped into the argument as if it were fresh dung and you were a dung beetle.
Python has plenty of serious problems. But if what you get hung up on is whitespace,
And there it is, you're a dung beetle white space Python fan who can't resist defending your bad decisions.
I don't understand the Rust culture, I really don't. You never see this kind of hardline, ultra-orthodox alignment with other languages, at this scale
Swift programmers were worse. It's a crappy language (has all the warts of Objective-C and adds some of its own), but as soon as you say "the enum system makes it easy to write confusing code" you will have all kinds of Swift programmers coming out to insult you and your dog.
I see, so if they can pass the data center inflicted extra costs on a large customer base, then it is okay. Thanks for showing just how thought-constipated is your reasoning.
The free market gave us rather dangerous smog in several cities and dangerous water before the EPA got on the case*. The private insurance industry (among others) is responsible for out of control medical costs, and it is not going to fix the problem or be part of a solution. OSHA shut down dangerous workplace practices that those nice corporation inflict on their workers*. NHTSA got rid of many dangerous practices*. Should I continue or are you so mired in "free market" double-speak that you are beyond reason.
*Well, they did before the current alleged administration.
Heavier than air flying machines are impossible. -- Lord Kelvin, President, Royal Society, c. 1895