3 ms·
Once I started reading about these issues a few years ago, I stopped using Alpine as a container base image, and started using Debian (the 'debian-slim' variant
by kelnos 3y ago
Once I started reading about these issues a few years ago, I stopped using Alpine as a container base image, and started using Debian (the 'debian-slim' variant). Slim is still larger than Alpine, but not by a lot, and does contain some extra functionality in the base image that's useful for debugging (most of which can be fairly easily removed for security hardening). Debugging random DNS issues is difficult enough; there's no need to make it harder by using intentionally-faulty software.
While I wouldn't call myself a fan of Postel's Law (I think "being liberal with what you accept" can allow others to get away with sloppy implementations over long time periods, diluting the usefulness of standards and specifications), I think at some point you have to recognize the reality of how things are implemented in the real world, and that refusing to conform to the de-facto standard hurts your users.
The fact that the maintainer only caved because the TCP fallback behavior is finally being made mandatory, and not because he's (very belatedly) recognizing he's harming his users with his stubbornness, also speaks volumes... and not in a good way.
- soraminazuki 3y ago> intentionally-faulty software > the maintainer only caved > he's harming his users with his stubbornness A gentle reminder that you're not entitled to other people's free labor. It's one thing to disagree with technical decisions made by the project, but the shaming and name calling is a bit too much.
- cikey 3y agowe are not entitled to it, but it was the sole reason why our team (and it looks like others did too) stopped using alpine and i believe that should be valid feedback to the maintainer.
- marcus0x62 3y agoThis is a ridiculous take. Nothing in the parent comment even remotely hints at feeling entitled to the labor of the Musl maintainers — they just disagree with implementation decisions that have been made. And while I’d agree in principle that nobody is entitled to anyone else’s labor for free, I’d also add that nobody is entitled to be shielded from criticism of work they have chosen to publish, or to have that criticism be watered down to a sanitized, milquetoast version of the writer’s intended message.
- camgunz 3y agoThe stuff op quoted: > intentionally-faulty software > the maintainer only caved > he's harming his users with his stubbornness is strong language and not productive. If someone at my company sincerely criticized my work in this way I'd find it unacceptable and managers would get involved. There's criticism and there's polemics, and this is the latter.
- marcus0x62 3y agoAs it turns out, HN is not your office and HR isn’t here to “get involved.”. Thankfully. I would agree there is a line, but disagree that the original poster stepped over it. Disagreement, even vigorous disagreement is important. Calling out bad technical decisions is important. Calling out oversensitive people who want to censor online discourse to their personal tastes is also important.
- soraminazuki 3y agoIf criticism is "censorship," you are very much censoring me too. FYI I didn't ask anyone's post to be taken down. Furthermore, ad hominem attacks have nothing to do with "calling out bad technical decisions."
- marcus0x62 3y agoNow, that is a ridiculous take. By your definition, censorious people have to describe themselves as such? The rest of us use "censor" as a term to describe the action of others.
- soraminazuki 3y agoNo, to censor means to remove speech and I have never defined it any other way. Calling out abuse for what it is hardly fits that definition. BTW go take my words verbatim and use it against me if my actions are genuinely hypocritical. But to do that for my actions you made up is abusive and makes you look bad.
- supazek 3y agoIm gently informing you that you’re being ridiculously oversensitive if you think that post needed to be policed.
- boringuser2 3y agoThis concept of ownership is questionable to begin with. If that maintainer abandoned the project, it would either be picked up or abandoned altogether if the project were worthless. It's a borderline case because it's almost worthless due to the aforementioned issues.