3 ms·
I don't think you miss anything. POSIX compliance is a headache which is not only hard to get right but also strongly limits your interfaces and internal tooli
by dathinab 7y ago
I don't think you miss anything.
POSIX compliance is a headache which is not only hard to get right but also strongly limits your interfaces and internal tooling.
Many scripts still will run with non full compliance, but that doesn't help if you try to build for OpenBSD.
Also I'm not sure how they ended up with 400 deps for coreutils. I would have expected much less. But yes this means at least until better code signing and so on is the default this isn't at all appropriate for the base of any OS.
I just which the author would have written it a bit less mean in it's wording. (Probably was just annoyed, but sill).
- lonelappde 7y agoThe author is from the 1990s era of Linux / FOSS, before kindness was part of the culture, when the culture had a tough competitive streak where mistakes and humility were seen as signs of weakness and disrespected. High expectations wee tightly bound with low levels of patience. And many people were scared off from contributing.
- saagarjha 7y ago> POSIX compliance is a headache which is not only hard to get right but also strongly limits your interfaces and internal tooling. Platforms which are POSIX compliant usually offer extensions and then allow for selecting actual POSIX-compliant behavior. It's not a very strong limitation if you're already fairly close to that anyways.