[object Object]
infrastructure admin for awful.systems, where the jank is a feature (tm)
- you can’t afford any new tech products, but none of them are for you. the only product categories are revenge porn and surveillance, and of course they overlap.
- none of the corporations doing IQ and neurodivergence tests will make the connection between their products being widely hated and their policy of only hiring people whose brains excel at bullshit tasks
- none of the people cosplaying as psychologists will draw a connection between discriminatory hiring pipelines and bullshit products made by people addicted to imposter machines. the numbers they made up to justify all of this still look fantastic.
- nobody will reflect on anything at all, actually. reflection is obsolete.
ah, there's muffins:
From: Richard Stallman Subject: Re: bytecode tail call optimization Date: Sun, 04 Jan 2026 21:56:30 -0500
[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
I am currently looking into the bytecode compiler. It seems that there's no tail-call optimization, is that intentional? Would it be a welcome change?
Tail call optimization would make programs faster but would make debugging harder. All in all, I think we are better not doing that.
As for implementation, Emacs bytecode is not like machine code. An optimized tail call in machine code can be as simple as adjusting the stack a little and jumping. For Emacs bytecode, several data structures about function call frames would have to be fixed.