Our great sponsors
-
wing
A programming language for the cloud ☁️ A unified programming model, combining infrastructure and runtime code into one language ⚡
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
terraform
Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
-
jsii
jsii allows code in any language to naturally interact with JavaScript classes. It is the technology that enables the AWS Cloud Development Kit to deliver polyglot libraries from a single codebase!
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
And it's a good question about the state! We should add it to the FAQ at the very least. If by state you mean persistent data in cloud resources, than our plan is to model that explicitly in wing resources and allow users to determine how these types of resources are handled during provisioning. https://github.com/winglang/wing/discussions/1054
I mean this one: https://github.com/aws/aws-cdk
This looks super cool, I'm eager to try it out on some toy projects. This might be a stupid question but how do you guys handle state, and by extension, secrets in state, one of the oldest unresolved issues in vanilla terraform? https://github.com/hashicorp/terraform/issues/516
The reason we chose to start with compilation to JavaScript and not some other popular cloud language is because JavaScript is currently one of the most used ones, and in addition, we are using JSII to write our SDK in Typescript and then export it for consumption in other languages, such as Go, Python, Java and others.
Reminds me of Darklang. Personally, I don't think vendoring cloud services into a language is going to be beneficial. I'm curious how the language deals with vendor updates. Do I have to upgrade the language then? If so, I see a lot conflicts coming from this. Then it comes down to Javascript or HCL, the HCL bit makes me think that the below statement is not as truthy as it is on the surface: