Systemd catches up with bind events

Posted Nov 13, 2020 22:42 UTC (Fri) by GhePeU (subscriber, #56133)
Parent article: Systemd catches up with bind events

So, to make it short, a project makes a breaking change, its downstream developers/users are initially blindsided by it, then they need to scramble to work around it, then they try to convince the upstream developers that the change is problematic and could they please reconsider but they’re told to adapt to the brave new world they now live in and fix their software, and finally they have to do just that and publish a new fixed release with a big disclaimer tacked on hoping that at least a part of the annoyed users that will be bitten by the change will read it and not complain about it to them?

The only news in this story is that, maybe for the first time, the systemd people are not the upstream project, and I think there’s a German word for what I’m feeling right now :)

Systemd catches up with bind events

Posted Nov 13, 2020 23:33 UTC (Fri) by ubhofmann (subscriber, #47368) [Link] (1 responses)

Schadenfreude? https://en.wikipedia.org/wiki/Schadenfreude

Systemd catches up with bind events

Posted Nov 14, 2020 7:03 UTC (Sat) by jonas.bonn (subscriber, #47561) [Link]

Besserwisser... ;)

Systemd catches up with bind events

Posted Nov 15, 2020 15:11 UTC (Sun) by Wol (subscriber, #4433) [Link] (1 responses)

> maybe for the first time, the systemd people are not the upstream project

Well, I think Lennart is well used to being downstream, and he likes to rely on upstream doing what they claim.

This seems a classic case of upstream not sticking to its promises, which is the whole problem with the unixy philosophy of being liberal with what you accept, and strict in what you emit. systemd (and pulseaudio, etc etc) is strict in expecting upstream to do what they promised.

Cheers,
Wol

Systemd catches up with bind events

Posted Nov 15, 2020 18:44 UTC (Sun) by NYKevin (subscriber, #129325) [Link]

> which is the whole problem with the unixy philosophy of being liberal with what you accept, and strict in what you emit.

That's not Unix, that's Postel's Law, which IIRC originates from TCP/IP (where it is *also* an unholy mess, but of a different kind).