48 points pmoriarty 17 hours ago 7 comments
sligbad 12 hours ago | parent
sgarland 58 minutes ago | parent
Gravityloss 26 minutes ago | parent
It's very error prone to describe a hierarchy of versioned software packages and configuration with shell scripts and yaml. Or use text files in git as a database. Or use the CI system as a bad substitute for a proper service (in order to do a simple thing, you must first create the world from scratch). And so on. Mainstream industry knows types, programming languages, relational databases, graphs and you name it, but those have not yet penetrated sufficiently into the infrastructure world. The understanding of the value of having types has been paid in sweat and blood when developing software and databases. Even a basic CRUD application with a basic SQL database will run rings around these Frankenstein monsters: in safety, speed, and extendability.
outworlder 11 minutes ago | parent
We have a multitude of configuration/markup languages all doing the exact same thing.
We have solved this problem in the 60s: S-Expressions. Should have just used that for everything. Configuration, code, websites, you name it. Infinitely extendable, easy to parse.
Thev00d00 21 minutes ago | parent
cmdrk 19 minutes ago | parent
jazdw 16 minutes ago | parent
I think you found the answer to that below - KEDA