News for hackers. Stuff that matters.
Re:The lost malloc() by tptacek on Wednesday November 04, 2026 @01:25PM (#50369554)
Malloc implementations are anything but boring!

https://csapp.cs.cmu.edu/3e/docs/dsa.pdf

Re:The lost malloc() by Mikhail_Edoshin on Wednesday November 04, 2026 @04:37PM (#50371915)
Malloc itself is not boring. What is boring and distracting is the need to think about managing memory when doing something else. (And we normally do something else.) Here the memory management part must be reduced to a mere technicality, some standard prologue/epilogue. It's not yet there, I think.
Re:The lost malloc() by cowlevel on Wednesday November 04, 2026 @09:04PM (#50374168)
GC languages do exactly that.
Re:The lost malloc() by Mikhail_Edoshin on Thursday November 05, 2026 @12:43AM (#50375629)
True. But GC takes too much control. Using Pythons as an example, first all is well, but then you need to turn it off selectively and have to learn first the whole concept of (reference-counting) GC and then augment it with a new concept of weak references. (Which are not just objects without GC, they are objects with more complex GC routines.)

A thing appears simple when it allows you to make distinctions you care about and avoid making distinctions you do not care about. C is weak with the latter, but Python with the former.

Re:The lost malloc() by cowlevel on Thursday November 05, 2026 @09:58AM (#50379895)
You can't give up control without giving up control...