mirrorbird (01:42:05)
i dunno what the costs are (HAHA that's the problem bird) but ideally the OS should just keep throwing at you "here's some spare stuff, use it, and be ready to give it up"

mirrorbird (01:41:36)
jit my java

mirrorbird (01:41:24)
yes. but deciding your allocation at compile-time is very 1990s

Agemixer (01:41:00)
yeah it could be a compiler. Which makes the final decisions how much RAM to reserve and where, to generate any slices of machine code.

mirrorbird (01:40:40)
if half the memory is fucking empty it is actually efficient to pre-allocate. but you try telling an autist.

mirrorbird (01:40:19)
haha, "reserving the memory to use all of it on demand" -- see also: people asking why SQL Server was eating 90% of memory. is something wrong? "NOT YET". you run other stuff, it will back down

mirrorbird (01:39:04)
'make...generate' is a lot of hand-waving. do we mean compile?

Agemixer (01:38:47)
afaik thete's no such compiler yet (unless we, say, chatgpt style but it's included in your program) Ehm

Agemixer (01:36:24)
so the generic (handmade) code would be just easy and small, the code generator would actually produce code reserving the memory to use all of it "on demand" even

Agemixer (01:33:57)
in fact if you were a damn good programmer, you can make it the machine generate the required optimized code for different situations, out of a generic algo feed to that little "AI"

Butterfly Syndrome

Interphace (Jan Reinert Karlsen)

djrandom

Time Left: 2:58