jobss: Ryan Zezeski's Memory by the Slab: The Tale of Bonwick's Slab Allocator, or, How I learned to stop worrying and love OO (youtube, talk) jobss: aka, Memory Managers, there can be only one! jobss: file this next to Goto considered harmful, and Trusting trust. jobss: extended here jobss: this is what is wrong. this is why we cannot have nice things. :-p jobss: actually you can use these strategies without needing to use actual Object Orientedness, but I what I take away from the video is that greatest efficiency gains occur when all memory allocation is done via a single object cache, and this is easy to enforce in an OO OS jobss: ie, this explains why totalitarian object oriented systems such as BeOS and OS2 'just work' while linux + OO just makes a horrid mess jobss: unless you give gnome or kde totalitarian control, and even then what browser do you use? jobss: lesson: someone needs to port a decent browser into the memory management space of one of these totalitarian objectish desktop environments to fix this crazy world jobss: see? jobss: see? jobss: maybe the last linked indicates that on OSX, google's web browser may be stable, since it uses a memory allocator like the one's described above jobss: I wouldn't count on it though, since (a) I didn't read the articles -- any of them -- (b) I bet the google team didn't either, (c) as soon as google's web browser has consumed apple's one in the market, then they will have no incentive not to make it into an abortion to destroy the apple OSX so that their own android/chromeos share can dominate further jobss: Note also, none of these articles actually justify the use of non-volatile memory paging at all in 2020, fwiw. It shouldn't be a default on any platform anywhere. Why is it always thrashing my USB stick? FFS jobss: (d) you don't care
