[lbj]

Its a nifty tool, but I can't help feeling a little disappointed that we're still having to deal directly with issues such as memory allocation in 2019.

[EpicEng → lbj]

Well 'we' deal with it so that you don't have to. What do you suggest? Somewhere memory needs to be allocated, this stuff isn't magic.

[asveikau → lbj]

Somebody's got to deal with it so that you may have the luxury of not dealing with it.

[chrisseaton → lbj]

How do you think we should be dealing with memory allocation instead?

[blattimwind → chrisseaton]

    addr = getrandom(8);
    mem = mmap(addr, len, PROT_RWX, MAP_FIXED|MAP_ANON, -1, 0);

[chrisseaton → blattimwind]

It's not realistic to use a per-allocation mapping like that in production - all your allocations will be scaled up to multiples of pages.

[jacquesm → chrisseaton]

Whoosh!

[saagarjha → blattimwind]

> PROT_RWX

Hmm…

[blattimwind → saagarjha]

The X is for fleXibility.

[rzzzt → saagarjha]

How else will you put the self-modifying code there?

[benj111 → lbj]

You don't necessarily.

Don't forget that theres memory managed languages that compile to c. They still use malloc under the hood.

[lbj → benj111]

Thats a good point.

[aaaaaaaaaab → lbj]

Right? Just use JavaScript already! /s