structringtxt

Finance is 100% figurative and has no 1:1 connection to consumption. We’re LARPing figurative truth of the before times to make the elders feel validated for accepting old semantics, and investment decisions we weren’t there to observe even happened; we just have to accept.

Progressives are demonized as violent revolutionaries to maintain the ruse. Most progressives on Main Street just want ALL their neighbors to be accepted in the local community. That’s turned into a fear mongering meme to empower government and maintain the public-private collusion occurring between politicians and aristocracy.

There is zero evidence aristocracy is necessary to maintain civil society and prevent reality from imploding. There is a lot of evidence of aristocrats invoking “end times are here!” if their figurative identity is questioned.

Go, Python, and every other known programming language have ecosystems, with syntax generators, validators, and SDKs for most APIs. Best part is I can hire people today who know how to use them.

AWS SDK for Go has snippets that just work right in the docs. Writing some logic like “if attempting to use AWS types a, b, c, or send values outside this regex, error” is not that hard.

Having learned Puppet, Chef, Ansible, and having zero use for them day-to-day in the current reality of “beam API params”, a problem specific DSL seems like a dubious proposition.

At the end of the day we’re structuring syntax in a file within the constraints of some compiler or interpreter, which itself is implemented as structured text.

Engineering is about keeping it simple. So I agree; we can avoid dozens of flavors of structured text (using up worker time to learn, compute cycles to use) and stick to general programming languages rather than prove how clever we can be by creating yet another tokenizer, parser, writer with some hand wavy, tangential connection to mathematical concepts.