On: Understanding Memory Management, Part 1: C

[keyle]

This is a silly argument because at the end of the day, once you make your code portable, you've now duplicated 99% of malloc and free, and you've left a mess for the team or next guy to maintain on top of everything else. You've successfully lowered the abstraction floor which is already pretty low in C.

[sylware → keyle]

what?? The whole point is to create independence, then create "real-life" alternatives. I don't understand your point.