we're gonna make everyone configure their Linux network interfaces like this:

<netIf kernelInterfaceName="enp3s0" name="bnx2_0" type="ethernet">
<autoInit/>
<addrobj type="static" name="default">
<address>
<internetProtocol version="4">
<fixedAddress value="10.1.12.225"/>
<fixedNetmask value="ffffff00"/>
</internetProtocol>
</address>
<routing>
<internetProtocol version="4">
<route tag="default" name="default">
<hop destination="0.0.0.0/0" router="10.1.12.1" metric="100"/>
</route>
</internetProtocol>
</routing>
<nameService type="dns" name="default">
<internetProtocol version="4">
<dnsServer priority="1" address="10.1.12.1"/>
</internetProtocol>
</nameService>
</addrobj>
</netIf>

@freya Nightmare :(
@sekka it's pretty!

@freya In my opinion, XML is not a human-readable language. Personally I can't express deeply enough how much I would absolutely hate that. It's better than binary configuration, but only barely.

I hate XML and its look-alikes with such an absolute passion that I don't even know where to begin.

@sekka huh. For us, it's the most readable thing out there, due to the tags being words and not an endless {}}{}{}{}{}{}}}}}}}{}}} that screenreaders literally do not read

@freya That's an interesting use case that I wouldn't have guessed, but makes sense. I'd prefer something like toml or .env, or just a plain ol' conf file, with all its limitations.

For me, xml is a giant blob of eye-hurting goo that I immediately nope away from.

@sekka @freya +9001%

Same with #YAML...

  • I'd rather start a better format like #YADL!

@kkarhan @freya Yeah, YAML is ... well, I see what they were trying to do.

I almost prefer JSON.