Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 5 Mar 2026 15:51:54 -0800
From:      "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com>
To:        dikshie <dikshie@gmail.com>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: jemalloc 5.3.0 upgrade
Message-ID:  <88DAD423-C980-4B28-8BAB-091F1CA19BCF@gmail.com>
In-Reply-To: <CAA1TSu_61d4f2%2BcoWWYqqxcvSNRcBO%2BsAMsJqRx_sZF8ATTRoA@mail.gmail.com>
References:  <CANCZdfrYrboDRQqmzrX2YSpwHUcn0gCLtuoxamcyvruNMG5shQ@mail.gmail.com> <ouy5xeom8hi.fsf@panix3.panix.com> <CAA1TSu_61d4f2%2BcoWWYqqxcvSNRcBO%2BsAMsJqRx_sZF8ATTRoA@mail.gmail.com>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]

> On Mar 4, 2026, at 1:04 AM, dikshie <dikshie@gmail.com> wrote:

…

> Now,  Facebook has unarchived the original jemalloc.
> 
> I just read the announcement in facebook's blog:
> https://engineering.fb.com/2026/03/02/data-infrastructure/investing-in-infrastructure-metas-renewed-commitment-to-jemalloc/

This should be interesting, given that Facebook/Meta has never really gotten itself together around stable release versioning: their whole philosophy is “release from HEAD”, much like Google (at least Google has made concessions with some of the projects it sponsors, like GoogleTest, though). Also, they do not have any interest in maintaining things beyond Linux or platforms that they ship their apps on (AOSP, iOS, Windows, etc), so I don’t foresee an easy path to maintainership on FreeBSD. Finally, Meta’s build process is tightly tied to Buck (a mutant of Bazel), so it’ll be interesting to see what happens in that regard as well. Moving to cmake would be positive, but Buck? Having to run Java/Nailgun to build a trivial library would be overkill (like using burning down a spider to kill a house).

I’d love to be proven wrong, but if past behavior is an accurate predictor for future behavior, I’m not going to hold my breath.

Kind of like Microsoft with the GitHub acquisition and all of the CoPilot enshittification that has ensued (not just in GitHub, but with all Microsoft products).

Thanks,
-Enji

1. Here’s a fun example: https://github.com/facebook/folly/releases . All tags are created automated by a bot, there’re no release notes for each release, and it’s unclear what kind of testing/qualification has been done for each release.
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkHfexGRJ3gYRdA2gGpE5DjPsNJgFAmmqFxoACgkQGpE5DjPs
NJiNdw/9HTGzG8kNkTU8KHLwfPNGByqA1cOi1/3eHCwH08o/lh5OXEe3AW8d/3Ss
s7mgWyPggJY0Eq646o+Y7LAs5qkJ7OCWyICoA+6WNswvrqLMnacvQahKiSNLI5Rs
goSzzBiFmjBvvUXiP5LaHOUSCxs9Bl3YtVLdF1iK5S6DYo2cmBkxu9bRN99IIaUQ
E4flFNLdReQVWLCscW1SSNdmSRDKDn+geOP2qpPbGd6K92jovmKBQpVVxeiBbbTE
twRhAieg8E5WY6vFrbrdpin9iKIKjAO12uHVlTqNLjSKiTRxHAWjy/uKL4wUXpQP
XW/CY40TB25M6UT8x3slbdfYq4U7ceDB9K0+q9iULz+BB3dPz0uDwKGAoNrunT0Q
i9jHxjsK+I+8Yu6aIrwlACfWf8sBkdIbwXPpmWX4osEItl7rDixI5kYFP1zbayBC
tiqCiXCwENlasmQVcO2M+7t6CAFRYr6me3zry5+u4/3d+a3+Z9by3vvJUSKkU8sC
Krxy+Ae1FTXaoRiFTlp5NvQrlYF/oDO21+qGrKdAQ7DaeefAlpWkt+lm2KleK0Zu
CkYM7p/ASyWDcsZXcPUPEVOxypm7+2yUWwglo312XZcgSar/O/Rnw/7DtshdObae
+VYTJNRlVS65JN/afi+YLJIdvl0G+Crv7nTMaISnZ4qYxlkOwIA=
=vCSB
-----END PGP SIGNATURE-----
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88DAD423-C980-4B28-8BAB-091F1CA19BCF>