Basically, my app is a memory hog. I went all-in on performance, and neglected frugality. Lots of caches, local copies, and pass-by-value.
I suspect the best solution will be architectural, which promises to be a pain.
I suspect the best solution will be architectural, which promises to be a pain.
A language choice is a starting point but you have to know the techniques of architecture learned.
That's the issue with the new "memory is cheap" model. I cut my teeth with 256 BYTES (not KB or MB) of space for the program, the stack, and the scratch.
But I've gotten sloppy, over the years.