On the sickness of our community

Posted Oct 13, 2014 17:48 UTC (Mon) by rahulsundaram (subscriber, #21946)
In reply to: On the sickness of our community by nim-nim
Parent article: On the sickness of our community

I am not sure how your reply addresses your claim. Technical choices for a configuration format has nothing to do with not being polite or trampling over other people's feelings.

to post comments

On the sickness of our community

Posted Oct 13, 2014 18:00 UTC (Mon) by nim-nim (subscriber, #34454) [Link] (6 responses)

It was treated the usual I am RIGHT everyone else is WRONG LP way (with "look how cool LP is" bystanders). json is gone in systemd without any apology (but more abrasiveness on other format alternatives)

On the sickness of our community

Posted Oct 13, 2014 18:56 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link] (2 responses)

Well, if anyone didn't think their choices were right, they wouldn't be making the choices they do. I don't see why a change in configuration format in an entirely different software requires an apology or to whom. Sorry but I still don't have much of an idea what you consider a problem.

On the sickness of our community

Posted Oct 13, 2014 19:01 UTC (Mon) by dlang (guest, #313) [Link] (1 responses)

> Well, if anyone didn't think their choices were right, they wouldn't be making the choices they do.

There's a difference between thinking that their choices were right and being unwilling to consider that they may be wrong.

good programmers, and especially good project leaders need to be open to the possibility that they may be wrong and listen to feedback.

On the sickness of our community

Posted Oct 13, 2014 19:05 UTC (Mon) by rahulsundaram (subscriber, #21946) [Link]

> There's a difference between thinking that their choices were right and being unwilling to consider that they may be wrong.

Sure and systemd has changed a lot based on external input. Abstract conversations OTOH don't accomplish much.

On the sickness of our community

Posted Oct 13, 2014 19:52 UTC (Mon) by johannbg (guest, #65743) [Link] (2 responses)

The polypaudio/pulseaudio community needed a way to describe some digital audio properties in a fairly standard and extensible way that wouldn't need protocol updates in the future and they settled on JSON.

As far as I know it was not a sole decision made Lennart so it would be good if you could actually reference that discussion when he declares that.

You need to be a bit more spesific what you mean by "json is gone in systemd without any apology"

On the sickness of our community

Posted Oct 14, 2014 12:53 UTC (Tue) by cortana (subscriber, #24596) [Link] (1 responses)

I don't even see any JSON in /etc/pulse, ~/.config/pulse. Nor has, to my memory, systemd ever used JSON except as one of the export formats in journalctl.

On the sickness of our community

Posted Oct 14, 2014 13:33 UTC (Tue) by johannbg (guest, #65743) [Link]

You should be directing these comments at nim-nim where I in the comment you responded to am asking nim-nim to clarify and reference to what he meant by Lennart solely deciding upon JSON in pulseaudio as well as what he meant by JSON being gone in systemd without any apology.