Herp derp I eat paste

A year and a half ago I made a kitchen clock, which has worked well (except that I had to swap out the screen which broke mysteriously).

But yesterday I was having some work done here, so I had to remove one of the wifi access points here, and… the clock stopped working. *gasp* Yes, because I had in my infinite wisdom decided that I would generate the clock face on a different machine, because the clock is a Raspberry Pi Zero 2 W, and I just assumed that it didn’t have enough memory to run Emacs (which I am, being a totally rational person, using to generate the SVG that’s being displayed).

So it’s a Rube Goldberguesque setup of having the image being generated on the main server, and then scp‘d over once a minute, and then being displayed on the console there.

But the wifi outage made me wonder — is it true that the machine doesn’t have enough memory to do it all on device?

So it’s got 416MB of useful memory, and while just running and doing nothing special, it’s using 129MB of that.

What happens if I load an Emacs with all the SVG libraries and stuff and generate the image?

It’s using 186MB — so the Emacs occupies about 50MB max.

*sigh*

It’s so easy to think of Emacs as this “big thing”, but everything has gotten so much bigger around it that it doesn’t matter at all any more.

So now I’ve changed the code to run on-device, so the only thing that goes AWOL if the wifi goes missing is that it won’t display updated temperatures.

Leave a Reply