fragmentation

Aren't lawn care providers already pretty much doing this by means of fragmentation?

Surely that can't be done in all circumstances without severe memory usage issues or fragmentation problems though.

With malloc you potentially have short-lived and long-lived interspersed with each other, creating lots of holes/fragmentation.

You can deallocate if you use small enough chunks, although you might need to use some other strategies to minimize fragmentation.

This creates fragmentation and a jungle of compile-to-JavaScript languages order of magnitude bigger than what we've got now.

Add to this malloc fragmentation and need to return word-aligned chunks of memory and you have a clear picture of what happens.

I'm not really following your fragmentation/consolidation line of argument or how it relates to the modern web...

>There's the issue of fragmentation Speaking of fragmentation.

Social fragmentation of information sources likely makes it even easier today...

ZFS doesn't slow down if the storage pools are full; the problem you described there sounds more like fragmentation, and that affects all file systems.

I believe the fragmentation started at Berkeley, and was greatly expanded by the mini-computer manufacturers.

The continued fragmentation of the industry has left merchants struggling to navigate necessary customization and even more difficult documentation; although Stripe has led well in this area.

Re "avoid fragmentation to begin with by storing objects of the same size in the same memory span." That's easy today, because we have so much memory and address space.

I am not so sure we would not." Considering the situation, anything other than annexation would have been foolish and would have put India in a far weaker position and could quite possibly have led to further fragmentation as well.

Fragmentation really isn't much of a problem anymore with modern mallocs like jemalloc and tcmalloc.