That's only a problem with some sans-serif fonts. This very site is using a sans-serif and the capital 'I' has bars in either end so it's not confused with 'l'.
Some sans-serif fonts do add little flourishes to some letters, like 'l', to further distinguish them.
According to the CSS, this site requests the fonts Verdana or Geneva in order, and what you say about the capital 'I' is true for the former but not the latter.
> That's only a problem with some sans-serif fonts. This very site is using a sans-serif and the capital 'I' has bars in either end so it's not confused with 'l'.
I'm not sure if my browser is broken or what but they literally look identical to me in your comment.
One place where the big i and small L look almost identical, and a pretty funny/annoying place for them to do so, is when you're typing a WiFi password in OSX (if you toggle "Show password"), at least as of MacOS Monterey 12.1. I also see them as almost identical in my browser's URL bar (Firefox 148.0.2 on aforesaid version of OSX) which isn't just an annoyance but might even be a security concern!
And that's the argument for serif. If you set sans serif the OS may pick one or another font, and that choice may change over time.
By publishing with serif you are guaranteed there will be a clearer distinction.
But txet is contxtual you can evn miss letres entrly yet be lgibl.
The over a hundred page long research paper makes conclusion off a practical study, not encumbered by intuitive clues that typically make us think serif lead to more legibility.
Not for me. The font we are all seeing depends on our browser and whether we have the requested fonts. No bars on the sans serif my Firefox on Android is displaying.
This might be a question of philosophy! I suspect that they were originally serifs - see inscriptions to Julius Caesar, say (such inscriptions being the inspiration for Trajan font) - but for some writers they were extended to become part of the letter body, akin to the bar on the top of capital-T.
My take then is, originally they were serifs, now they are sometimes part of the letter form.
The squash and stretch effect is certainly not to my taste but it's a personal site, where people should feel they can try things out. I do think the effect should be disabled when users have "reduce motion" enabled.
And its binary is banned on certain macOS installations. I have two identical mac minis with the very same OS version. On one cron runs, on the other the cron binary doesn't run (killed: 9) even if I re-sign the binary in different location with my own codesigning identity. It's that banned.
Why would Apple "ban" a binary they ship with the OS? If I just run /usr/sbin/cron on my Apple Silicon Mac, the output is "Killed: 9" but if I actually create a crontab for a user, it works.
That's fascinating. I'd love to see a shasum tree of both OS installs to know if this was due to some path-dependent upgrade sequence one of the machines went through; or whether this is down to some sub-model-number hardware-component stepping issue with power efficiency or something, that only one of the machines is affected by, where the implemented launchd solution is "don't let cron run."
The one machine where cron was working, had crontabs prior to upgrade to 15.x. The other had none.
I have googled back then and discovered that yes Apple specifically want us to suffer with their braindamaged launchd instead of cron, and thus they went to extraordinary lengths to get rid of working tools.
Anyway, cron is easy to rebuild from sources, so that's what I did.
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)
Some sans-serif fonts do add little flourishes to some letters, like 'l', to further distinguish them.
reply