3 ms·
> I don't want to write all of my stack in a cloud programming language. Especially one that is completely new and not cross-compatible with any other language.
by acdha 4y ago
> I don't want to write all of my stack in a cloud programming language. Especially one that is completely new and not cross-compatible with any other language. This isn't just a small thing -- it's a complete dealbreaker. There's no tools, no libraries. It's been a decade since Nim has started development and look at its progress now with so much interest behind it. Creating PLs and compilers follows the 80/20% rule.. it will take mountains of work to even make the compiler truly optimized and usable, and that's a basic prerequisite.
I think this is especially important in this space. If I use Terraform, in addition to tons of tools and experience in the community, there are a variety of mature tools for things like compliance and cost checks. If I use AWS CloudFormation, the same is true. That doesn't mean I wouldn't consider a new tool but it would have to be especially valuable to make up for the cost of losing that baseline.
- shaiber 4y ago[Wing team member here] Wing compiles to JS + Terraform, so all your downstream tools function as they did before
- acdha 4y agoAh, that’s an important detail since it makes it a lot easier to fit into an existing pipeline then. How’s the escape hatch if you need Terraform features which Wing doesn’t already support?
- shaiber 4y agoWe're still working on it. You are welcome to join our GitHub and help influence what shape it will take. Additionally, you can create your own resource, or a target for a resource if you find the one that comes with the standard library lacking.