2 ms·

If it were created today rust might be a good option, although in the early days of rust, it probably wasn't mature enough. Although, it does require some amoun

by thayne 4y ago

If it were created today rust might be a good option, although in the early days of rust, it probably wasn't mature enough. Although, it does require some amount of memory management, but to a lesser degree than c/c++. > Go offers a nice balance between performance and platform agnosticism I don't disagree with this. It's too bad the language itself has major problems (which I won't get into here). > I'm on the opinion that a DSL is better The two aren't mutually exclusive. What I want is a DSL embedded in a full programming language, like chef's dsl in ruby. > You want your infrastructure declarations to be easily readable and supportable. Absolutely. > Anyone who has used Terraform can read any HCL; your Python code doing the same could be terrible and unreadable by anyone not already on your team It's possible to write terrible and unreadable HCL too. I know because I've written some. > In any case, there's cdktf now, you can mix and match terraform with cdktf. Unfortunately, I haven't had a chance to look too deeply into it yet, although I definitely want to.

sofixa 4y ago
> The two aren't mutually exclusive. What I want is a DSL embedded in a full programming language, like chef's dsl in ruby. I've seen some atrocious Ruby for Chef, so I'm not sure I'd agree here. The advantage of a DSL is that it limits how far you can go. In the case of HCL pre-v2, it had some limitations around dynamism, but now that's out of the way IMHO it strikes a decent balance. You can write hardcore HCL, but IMHO it's still way easier to parse by a human that bad Python or JavaScript. As for CDKTF, I'd recommend you do. You can mix and match like having a project with CDKTF in e.g. Python or Go use regular TF HCL modules, but also vice versa, defining a module in TypeScript and consuming it from regular Terraform. So you can have the extra flexibility ( with all of it's advantages and risks) on a per module basis, not all or nothing.

by thayne 4y ago

sofixa 4y ago

> The two aren't mutually exclusive. What I want is a DSL embedded in a full programming language, like chef's dsl in ruby. I've seen some atrocious Ruby for Chef, so I'm not sure I'd agree here. The advantage of a DSL is that it limits how far you can go. In the case of HCL pre-v2, it had some limitations around dynamism, but now that's out of the way IMHO it strikes a decent balance. You can write hardcore HCL, but IMHO it's still way easier to parse by a human that bad Python or JavaScript. As for CDKTF, I'd recommend you do. You can mix and match like having a project with CDKTF in e.g. Python or Go use regular TF HCL modules, but also vice versa, defining a module in TypeScript and consuming it from regular Terraform. So you can have the extra flexibility ( with all of it's advantages and risks) on a per module basis, not all or nothing.