Would have been nice if the article discussed protien quality and compared the quality of peas and lentils against other common sources like whey and soy.
My understanding of the system webview is that applications can share the resource instead of each using their own copy, reducing memory usage and improving multi-tasking. Facebook's solution seems to side step that benefit. I use the fb browser much less frequently than my normal browser, and id rather not use the fb browser at all. I imagine this is true for most users, so the security benefit seems overstated.
The unique thing about the US healthcare system is that care is directly proportional to how much money you can spend on it. So as a top spender, yes the care is great. Though realistically we should look at the system as a whole for all people it "covers". Looking at infant mortality rate, life expectancy, etc, for the average person, the picture is bleak; the US is shockingly bad.
They added the addictive "superior" to describe mysqls implementation in their docs. That's the entire change. No code changes. Seems like a petty change antithetical to good documentation.
In my experience, a GUI can chain command together for you and invoke them instantly or automatically, no typing, no looking. It would really help to understand what tasks you're doing that you feel CLI excels. They're certainly git commands GUIs handle poorly, but they are usually arcane and infrequently invoked. I'd hope you'd agree there are cases where the GUI excels.
How is muscle memory an exclusive benefit of CLI? How is response time superior for a CLI? I've used GUI tools for git professionally for years and it seems much faster, safer, and easier to use. I've had peers that use CLI instead and they appear to struggle for all the expected reasons (poor feedback, poor discoverability, etc).