Re:Infrastructure as Code, Part One
by argd678 on Saturday April 13, 2019 @08:41PM
(#19656758)
These inheritance constructs are either missing or too ridged in the current tooling to be able to use those patterns unfortunately. Java in a lot of ways seems like an ideal language, especially with AOP, where for example you could use exactly the same code and swap out the cloud provider.
[ Parent
| on HN ]
Re:Infrastructure as Code, Part One
by joshuamorton on Saturday April 13, 2019 @10:02PM
(#19657092)
I agree that most languages are bad for this. I think Java is also too verbose to be a good config language. My experience has been with a Python dsl but I'm open to other options too.
I actually see it less as a configs language issue and more that you want a program that encapsulates the patterns and logic for your app to run. So the language itself is a bit less of an issue other than it needs to support the model you’re creating.