Yes and no. As a Software Engineer and as someone who loves automation,
the move to files that are more easily parsed by software allows us to
get closer to the linux mentality of making small components you glue
together. It also allows for pre-written libraries to be used to parse
the file into data objects in the code.
At least it's not XML.
On 05/08/2018 04:32 PM, Mike Small wrote:
Richard Pieri <richard.pi...@gmail.com> writes:
And here is the rough equivalent for Netplan:
network:
version 2:
ethernets:
enp0s31f6:
addresses:
- 192.168.1.202/24
gateway4: 192.168.1.2
nameservers:
addresses:
- 192.168.1.202
search:
- rgo.gweep.net
Excessive use of YAML and JSON seem one of the current maladies among
developers. I'm starting to notice command line utilities with JSON
output options too, e.g. lsblk. Hmmm, well, maybe that would be handy
to certain people who use certain languages, but it seems like bloat.
OpenBSD remains quite usable. Can't beat them if the question is one of
good design taste, IMO. At least I don't find myself constantly
scratching my head wondering who had an issue with the old incarnation
of a revamped (for the 2nd or 3rd time in some cases) subsystem there
like I do with Linux. You won't find as many device drivers of
course.
_______________________________________________
Discuss mailing list
Discuss@blu.org
http://lists.blu.org/mailman/listinfo/discuss
