3 ms·
> The first is that using a different libc helps finds bugs in programs that assume that every system uses glibc. I praise the author for taking this work upon
by ed25519FUUU 4y ago
> The first is that using a different libc helps finds bugs in programs that assume that every system uses glibc.
I praise the author for taking this work upon himself. As for me I don’t want anything to do with being a bug canary for other developers. I’ll take time tested and stable thank you.
- sudobash1 4y agoIt depends on your usage. If you use software from the stable releases (not edge), then the testing should already be done for you. And with the rise of Docker/Podman containers, Alpine sees a lot of testing. Because of the simplicity and compactness mentioned in this article, it is very popular in Docker containers. So it has a very wide deployment and tons of testing going into it. Personally, I value a lean and simple OS enough that I am willing to risk finding these bugs. Alternatively, you can try Void Linux. It is similar, except that you can choose between a glibc or a musl install. I've not used it yet because it is rolling-release only and that doesn't fit with what I need it for currently.
- zamadatix 4y agoIn the end many packages just aren't in the stable (or any) repo for that reason. If it's there you're golden, if it's not you're just kind of left hanging.
- majou 4y agoHere you're electing to remain on the happy but bloated path. However sometimes it may be worth to venture out a bit in exchange for reducing code, or for using code that aligns more with your philosophies.