I think proportion is more useful that quantity. 66% of housing units (that's all forms of housing, not just single-family homes) have a garage or carport. Also, given that there are ~145 million housing units, 60 million would be a bad situation.
> most are within 100 miles of a fast DC charger
That's not good enough. No one can spend 3-4 hours to drive 200 miles round trip, or even 100 miles, to charge quickly.
There needs to be a good solution for the 33% of households that don't have access to EV charging as part of their home. Until it becomes really plentiful, part of the solution may involve fast charging that only the 33% can use or that favors the 33%; people who can charge overnight at home should charge overnight at home.
Fast chargers colocated at grocery stores people shop at at least weekly are a solution, Tesla did this (Meijer partnership), as did Electrify America. Walmart is rolling out charging at most of their US stores. Home charging is a solution, but so is workplace level 2 charging.
Can you charge at home? Do so. Can you charge at work? Do so. Can you charge at a grocery store or other location your task will take longer than the charging? Do so. This works for most Americans, while charging infrastructure continues to be rapidly deployed. The gaps will be filled, how fast is a function of will and investment.
Chargers at grocery stores and other places of public accommodation that have lots of parking and customers who stay a while are good options. I don't know how many are enough; even fast chargers take orders of magnitude longer to use than a gas pump.
At least in the midwest very few grocery stores have fast charging. Usually the fast chargers are along highways on the outskirts of cities, and even then they’re almost always at gas stations.
Agreed. However, the number of people who live 100+ miles from a fast charger rounds to zero. Something like 85-90% of the US population lives within a metro area, and even in the least "EV friendly" states probably has a fast charger within 10-20 miles at most.
And that would be OK as a clue if Silverstein was a red herring, Grizzly was also a children's author and Scarry sounded like scary (and also meant something in the same ballpark as Gory, Grim, and Grisly)
Safari (desktop and mobile) also has tracker blocking built in. "Prevent cross-site tracking" and "Hide IP address from trackers" are two settings it has; I think the first is checked by default, I don't remember about the other.
In the DevTools network pane, it shows requests to known trackers, like Google Tag Manager, being blocked.
Try using Amazon in Safari sometime (in Lockdown Mode, no less): non-stop ads (some which flash), sponsored results dominating the first page of search, random Dufus pop-ups forcing AI. You can hide "distracting" elements but they just appear again later. Safari is not a user-friendly browser.
Safari is my default browser. I don't know what "Dufus" means, I don't recall any A.I. references. On Amazon, it's all first-party stuff, what browser blocks that natively? It seems like you're comparing using Safari without an ad blocker to a different browser with an ad blocker.
I know the most popular ad blocking extensions don't make a Safari version but there are ad blockers for Safari.
I don't get any of that in Safari or any other browser. "Rufus" is just a button in the main navigation, between "All" and "Same-day delivery" that I ignore. On individual product pages, there's "Ask Rufus" stuff in a couple of pages but it's no worse than other content I scroll past and seems just like previous features that didn't have a named AI identity.
Yes, the tabs in a tabs pattern should be keyboard navigated using arrow keys (ironically not the Tab key).
Also, the summary for the currently open details element will have the wrong state, 'expanded' instead of 'selected'. And while a set of details can now have a maximum of one open at a time, you can't ensure exactly one is always open (without JavaScript) as the tabs pattern requires.
That's not correct. There is no aria-open attribute and the summary implicitly has the correct ARIA state, aria-expanded, indicating that its details element is either expanded or collapsed.
There have been bugs in its implementation, particularly in Safari and differing between mobile and desktop Safari.
Yes, Google started revealing the contents of <details> a few years ago, long after the element was supported in all browsers. Firefox added support earlier this year and Safari just added it.
Supporting the behavior was related to changing the user agent CSS when they're closed and the other browsers implemented it and hidden=until-found at the same time.
> most are within 100 miles of a fast DC charger
That's not good enough. No one can spend 3-4 hours to drive 200 miles round trip, or even 100 miles, to charge quickly.
There needs to be a good solution for the 33% of households that don't have access to EV charging as part of their home. Until it becomes really plentiful, part of the solution may involve fast charging that only the 33% can use or that favors the 33%; people who can charge overnight at home should charge overnight at home.
https://www.energy.gov/eere/vehicles/articles/fotw-1268-dece...
reply