something's up. i can start moving things with my mind. autoconf is yielding its massive power to me
and on another note, i'm still incredibly upset whenever i see it that c++ modules are actually the shit and also you can't use them without cmake. thats fucking intolerable
given that i am now confident i can make the choice between c and c++ a dynamic decision process around bootstrapping and dependencies and even intersperse them in the same family of projects (monorepo), i feel something has to be done about the module interface
cc @whack i'm trying to hype myself into making a Good C build system. i have an insane idea of what components are necessary. may be wrong
i was very seriously going to make python faster but i'm not doing that unless someone is paying me. and its bootstrap story is still too fraught for no reason
spack has a patch to remove openssl from cpython but it's not enough. we have to remove everything
@hipsterelectron interview question, for a range of viewers: what's your opinion, on "c is filthy unsafe boo boo", and safe ABIs like fil-c?
@promovicz i don't understand the predilection towards describing C as if "unsafety" is a fundamental problem at the core of its being. actual semantics according to the C standard are in fact the closest thing we have to mathematics, law, and computer science all joining forces together like we will during the revolution
@promovicz the term "memory-safe" is a dead meme. corps killed it. we built it. i count myself in that hallowed group
@promovicz concurrent garbage collection is not an answer to memory safety. it's a complete diversion. either you approach the problem of sharing access to a finite hardware resource or you don't. rust tried. the c standard succeeds.
@hipsterelectron about GC and concurrency control I'm like "we just need control and modularity of processes and side-effects", but i fear they're going to standardize another Common Lisp before the means of production can be sufficiently re-owned.