4 ms·
One can argue that maybe networking functions shouldn't be part of the C standard library, but maybe a hypothetical "libos" instead, sort of like how Rust has l
by moosingin3space 9y ago
One can argue that maybe networking functions shouldn't be part of the C standard library, but maybe a hypothetical "libos" instead, sort of like how Rust has libcore, libcollections, liballoc, and libstd separated.
I wonder if modularizing libc is at all feasible. Linux lets you use multiple libcs, so (at the expense of a more complex build) it should be possible there, at least?
- kmicklas 9y ago> Linux lets you use multiple libcs, so (at the expense of a more complex build) it should be possible there, at least? Linux lets you use no libc if you want, too. I suspect the reason this kind of change doesn't happen is, if you want to make breaking changes like splitting libc, then you might as well fix all the crap APIs, at which point you might as well fix the crap language choice (and use say Rust instead) at which point libc is a low level abstraction that you hardly care about.
- bluejekyll 9y agoI asked this in the Reddit discussion, or something related. I'm thinking it would be interesting to have std::net offer options for swapping in different DNS resolvers, for this specific case, and probably would be interesting if it offered this option for any/all libc functions, especially around network operations.
- deleted 9y ago[deleted]