Stop calling malloc()

Memory should be free

@lunarised Wanted a chunk of memory anyway? We already had that, it was called static arrays.

@wolf480pl

Seriously, since a couple years I wonder if one can always replace malloc/free with forks.

I think that it should be possible to prove that you always bind memory to processing, and there is no other reason except programmer lazyness to do such processing in the same process.

Counter-argument: sed hold-space processing.

Counter-counter-argument: you just need more expressive pipes and redirections, and instead of one single hold-space, you'd get multiple spaces each connected to simpler version of sed.

Counter-counter-counter argument: that's cheating, as the pipes would handle memory growth under the hood in kernel space.

But... why not?
Userspace programs would be way simpler (and safer) without malloc/free.

@lunarised

@Shamar @wolf480pl @lunarised There is a lot of cases were you absolutely need to use malloc.

For example graphical applications need a buffer to contain the whole pixel array, this need to be dynamic.