of course the toml crate has serde on it
Replies:
15
steve klabnik jumpscare https://stackoverflow.com/a/31778003 yeah i'm sure the one guy whose entire job is making snide remarks about copyleft on podcasts is the authority on what glibc is or isn't gonna do
i already nerd sniped a glibc dev into supporting posix_getdents() it'll be so funny if glibc gets it before the rust libc wrapper crate
lest we forget like two years ago the rust community's concerted campaign to neg the musl maintainer repeatedly for not optimizing the malloc impl for the specific allocation profile of the rust compiler
i totally forgot about that until just now wow. entitled doesn't describe it
maybe if you care about allocation so much you can link a dedicated allocator?????
that's actually what i'm doing right now but it makes me feel bad to be taking advantage of the result of a widespread coordinated harassment campaign against a maintainer whose work is a fucking pillar of half the world's secure software
pretty confident nobody was offering him cold hard cash for that shit
i'm trying to think of a name for the bootstrapping task engine whatever the hell thing
maybe i can reuse the name capillary
it's more of the heart than the capillary. maybe the lungs
well no because it's not trying to do lots of build jobs in parallel at once or whatever. it's trying to be like a ghost. in the walls. making connections and disappearing
looks like i only ran git init for capillary so honestly i'm going for it. it's a good name and it's the kind of name an insane person (which i am) would use and that's what i'm going for
what i'm actually gonna do (which i'm so fucking pumped about) is use the zip crate that i keep fucking around with so that i can make the bootstrap utility into a self-extracting container format. like john sirois's scie-jump https://github.com/a-scie/jump
i'm not too worried if there's a lot of overlap with the scie-jump project because that came out of our collaboration together at twitter in 2019-2020 that led to pip install --report. sharing code would be good but i think the approaches are meaningfully distinct
