>the association of well-being with regularly eating potatoes was nearly as negative as the association with [social media] use.
Maybe regularly eating potatoes is a lot worse for a person that most of us currently realize. (They do have an extremely high glycemic index and high levels of oxalic acid.)
Yes, many US businesses are eager to hire illegal immigrants because they work for less, but they're also eager to hire legal immigrants because they will work for less than citizens will.
I wonder whether some fraction of the population has shit night vision and whether this fraction's preferences are driving this trend to too-bright headlights.
That would explain scenes on TV and in movies with very low "key", which to me are awful and frustrating because I cannot see anything, but maybe that is just how the (dimly-lit) scene would actually look in real life to the cinematographer or editor responsible for the visual design of the scene.
You’re jumping to the conclusion that there’s another reason they’d arbitrarily leave out such a segment. It’s either because there aren’t enough to merit an entry, or there’s some conspiracy afoot to make this obviously racist enforcement appear racist.
I don't need the OS to do that because Emacs will do it. I need the OS however to pass fn-N and fn-P to Emacs (instead of the default behavior of interpreting them as Expose shortcuts) and it does not seem possible to configure that without turning off SIP.
Similar story here. I used vscode for about 3 months for all my editing needs without even having Emacs installed, but returned to Emacs because of how hard it was to learn how to modify vscode (I'm not a web dev) compared to modifying Emacs and because of a vague impression that vscode is slower in responding to my inputs.
It's definitely slower when doing any intensive background activities that Emacs would normally offload. But I've found VSCode has features readily available as one-click installs that are very difficult and convoluted to setup in Emacs. For some of those you end up either settling for less-ideal tools in Emacs, or because you're not an expert in the specifics of the tool being integrated, you end up with a much less optimized integration. And in either case you can actually end up with a net-worse performance in Emacs, even though the VSCode core is in a far less performant language than Emacs.
> It's definitely slower when doing any intensive background activities that Emacs would normally offload.
Emacs is single threaded and can't offload any elisp code. Even the stuff it can offload as background OS processes report in to the main loop and share time with editing, so a chatty background process can and does frequently lock up Emacs. So I'm surprised that VSCode, whose runtime is better suited to async jobs, ever feels slower than Emacs.
I actually agree with that. I should have added a qualifier to my previous comment (grandparent), namely, I use Emacs mainly for things other than programming, and if I ever start programming full-time in a language other than Lisp, then, yeah, (for the reasons you give) I'd probably use vscode instead of Emacs to do that.
I use Emacs for managing files (with Dired) running shell commands, bookkeeping, keeping notes and chatting with LLM services.
ADDED. Because the new functionality will be used to create cutesy effects for reasons that have nothing to do with communicating math, increasing the demand for moderation work.
Why? Latex is not how maths if supposed to be read, else we'd all be doing that. It's how it might be written.
edit: Nobody is going to use maths for cutesy effects. Where have you ever seen that happen? Downvote them if they do. It is not going to be a big deal.
reply