I've found that Baldur's Gate 3 will warm up my apple silicon (everyday tasks do not).

Is that running on Rosetta 2? Rosetta 2 does (or did, maybe it's removed now) a fine job running x86 code on Apple Silicon, but boy was it cycle-hungry to do it.

Apple Silicon is not really the simultaneously silent and quiet and cool system it was in the M1 days.

If you get a MacBook Air it will get quite toasty at throttling limits. After all, it has no fan.

MacBook Pro models and Apple computers in general tend to favor quiet operation over keeping the laptop surface cool.

Many PC gaming laptops go out of their way to keep warm air off the keyboard deck with a high willingness to use fan noise to accomplish that since the assumption is that you’re resting your hands on the computer for an extended period and you have headphones on for your game anyway.

I probably should have clarified that I'm on an M1 then (a macbook pro, so there is a fan). I didn't realize the newer ones get warmer.

BG3 is a native game, they dropped x86 support shortly after launch on macOS (or maybe even in beta)

For context - the top answer was written by Bill Thurston, who was awarded a Fields Medal. (Kind of like a nobel prize for mathematics.)

I don't see how this is going to work when every application decides to ship and run a 4GB model, competing for video memory. It's going to be the Electron problem times 10.

Yeah, I think that's what the program creates in your github account. I see the source to those files embedded in the executable. (I'm not running the executable, but I downloaded the linux one to my mac to take a look inside.)

For caveman debugging, if I'm not sitting in a monad, I usually reach for something like Debug.Trace. Typically that's in Idris or my own language, but I see that haskell has it too.

For my own language, I have the syntax highlighting set to put the `trace` keyword in red, so I can easily clean up.

Historically, quite a few languages were (or are) vigesimal. Perhaps decimal is also unnatural.

It's been at least eight score since vigesimal usage was common in English.

It's still used for numbers between 70-99 in French, which is maddening when trying to copy down a phone number as a non-native speaker.

Yeah, I think Swiss French had more? (It's been about four decades since I took French, and high school classes are not very effective.)

French speaker here. (My native language is English but I learned French in France years ago, and can still speak it with near-native fluency). You're correct. French French (that is, French spoken in France, it's slightly confusing that the language's name and the country's adjective are the same) goes "cinquante, soixante, soixante-dix, quatre-vingts, quatre-vingt-dix, cent". In English, that would be "fifty, sixty, sixty-ten, fourscore, fourscore-ten, a hundred". But Swiss French goes "cinquante, soixante, septante, octante, nonante, cent", which would translate to English as "fifty, sixty, seventy, eighty, ninety, a hundred".

There is an app for that, too: https://michelf.ca/projects/sim-daltonism/

It has a little window you can move over the screen to simulate a few varieties of color blindness.

The other day they blocked me from accessing Kagi's web site because I was using Kagi's web browser.

I was bit by this years ago when our test cases failed on Linux, but worked on macos. pdftotext was behaving differently (deciding to merge two lines or not) on the two platforms - both were gcc and intel at the time. When I looked at it in a debugger or tried to log the values, it magically fixed itself.

Eventually I learned about the 80-bit thing and that macos gcc was automatically adding a -ffloat-store to make == more predictable (they use a floats everywhere in the UI library). Since pdftotext was full of == comparisons, I ended up adding a -ffloat-store to the gcc command line and calling it a day.