News for hackers. Stuff that matters.
Re:Jemalloc Postmortem by charcircuit on Friday June 13, 2025 @12:51AM (#44265779)
Meta has a fork that they still are working on, where development is continuing.

https://github.com/facebook/jemalloc

Re:Jemalloc Postmortem by burnt-resistor on Friday June 13, 2025 @07:55AM (#44267708)
They take everything FLOSS and ruin it with bureaucracy, churn, breakage, and inconsideration to external use. They may claim FOSS broadly but it's mostly FOSS-washed, unusable garbage except for a few popular things.
Re:Jemalloc Postmortem by umanwizard on Friday June 13, 2025 @02:06PM (#44270739)
React, PyTorch, and RocksDB are all extremely significant. Not to mention them being one of the biggest contributors to the Linux kernel.
Re:Jemalloc Postmortem by nh2 on Friday June 13, 2025 @08:37AM (#44267968)
The point of the blog post is that repo is over-focused on Facebook's needs instead of "general utility":

> as a result of recent changes within Meta we no longer have anyone shepherding long-term jemalloc development with an eye toward general utility

> we reached a sad end for jemalloc in the hands of Facebook/Meta

> Meta’s needs stopped aligning well with those of external uses some time ago, and they are better off doing their own thing.

Re:Jemalloc Postmortem by nh2 on Friday June 13, 2025 @08:41AM (#44267988)
But I'd like to know exactly what that means.

How can I find out if Facebook's focus is aligned with my own needs?

Re:Jemalloc Postmortem by ahartmetz on Friday June 13, 2025 @07:33PM (#44273181)
Now: Benchmarks :) Long term: you can look at the past and guess