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.

> and need to be prepared to manage things like upgrading firmware

At one point in the early 2000's, my brother was soldering new capacitors onto dell raid cards. (I like to call that full-stack ops.)

I know it is out of scope for this article, but there are variants where the operations are monadic rather than applicative and the shape of the graph can change depending on values. And also variations with state - where history can be taken into account.

Jane street briefly summarizes some options here: https://blog.janestreet.com/breaking-down-frp/

And they have an interesting talk on the trade-offs and how their own system, incremental, evolved: https://blog.janestreet.com/seven-implementations-of-increme...