3 ms·
the main issue i see is musl: they have an history of not acknowledging bugs and disregarding standards last big issue i remember is they not implementing fall
by znpy 2y ago
the main issue i see is musl: they have an history of not acknowledging bugs and disregarding standards
last big issue i remember is they not implementing fallback-on-tcp when getting large dns record replies, so some dns record resolution would fail. the standard clearly says to switch to tcp under certain conditions, but they did not.
the bug was reproduced and reported, they refused to acknowledge it and kept the issue for a lot of people for a long time (at least one year iirc). they eventually relented and and implemented the correct behaviour.
call glibc what you want, but at least they don't have such dumb issues and that attitude.
- 3abiton 2y agoYou can always install incus and glibc. Went with musl for voidlinux, and for using certain appimage, I needed to have glibc. It was seemless to install incus, a debian image, and you have unlimited deb packages at your disposal.
- NewJazz 2y agoIs it just that one example? And the situation now is they "relented"? call glibc what you want, but at least they don't have such dumb issues and that attitude. I... Don't know what to say. You really can't think of one decision that the glibc maintainers have made that caused a lot of pain for users? Pretty sure the musl author has/had a blog post full of them. You don't write c library for no reason at all.