4 ms·
We should all just write our config in JavaScript or TypeScript because then we can standardize around a common interface language. It’s simple, widely known,
by bionhoward 6y ago
We should all just write our config in JavaScript or TypeScript because then we can standardize around a common interface language.
It’s simple, widely known, has comments, not dependent on white space, JSON has the right types we need program (and can be validated, with JSON Schema).
Critically, to generate configs, we can write loops, conditions, ternaries, functional programs with Ramda, classes/OOP, and even fancy GUIs. Simple English JavaScript is powerful and readable.
.js is the move here... especially once node supports immutable data structures
This is why stuff like AWS CDK and Pulumi are legit. Configure your stuff with actual code.
All we gotta do is fill the gap between JS and Python in terms of scientific computing, and we’re set. Typescript->WASM could be interesting.
I’m sure there are some details that make this difficult but, what do you guys think about standardizing around JS/TS?