7 ms·
Why is this a language, not just a framework for JavaScript or whatever? I suppose you could say the same about Terraform using HCL - but that makes extensive
by OJFord 4y ago
Why is this a language, not just a framework for JavaScript or whatever?
I suppose you could say the same about Terraform using HCL - but that makes extensive use of it being declarative, which is so unusual that they'd be picking an obscure probably-new-to-the-user language anyway. This just looks.. JS-ish, a bit like anything really.
I suppose I'm asking what are the language features that make Wing great for 'cloud', any `new Bucket()` etc. aside?
If you look at its 'design tenets', the only ones that are about the language not the SDK are just saying 'be good/familiar like other languages'... Ok so why not be another language? https://docs.winglang.io/reference/spec#02-design-tenets https://docs.winglang.io/reference/spec#02-design-tenets
- jakewins 4y agoIt seems because of the compiler tool chain? Eg this language can be “compiled” to terraform manifests. To do that with JavaScript or python you’d need some really strong static analysis to work out what to do if the user, say, writes a function that returns a list of new buckets to create, or whatever. Eg the argument seems to be the ability to statically deduce the required underlying cloud resources the code is talking about
- angio 4y agoOn the other hand the example on the landing page looks very close to what I can do with Pulumi (in Typescript) already.
- paulgb 4y agoI’m a fan/user of Pulumi, but this doesn’t feel similar to me. In Pulumi you write code that describes infrastructure, separate from the application layer code you’re deploying. This appears to be using application code to derive infrastructure config automatically. It’s a but like the https://www.shuttle.rs/ https://www.shuttle.rs/ approach. Edit: after taking a deeper look, a more accurate description might be that it allows you to embed application code within IAC.
- OJFord 4y agoBut you can generate e.g. terraform manifests from any language without actually compiling (or transpiling) to it? That seems barely more than an implementation detail: I get .tf or whatever I want at the end of it, that's all I care about isn't it?
- rmbyrro 4y agoIf a library is provided for developers to express the cloud stuff (including custom types), then I believe zero or close to zero static analysis will be needed.
- dohman 4y agore: Why is this a language, not just a framework for JavaScript or whatever? One product that's taking this approach is shuttle -> https://www.shuttle.rs/ https://www.shuttle.rs/ (disclaimer: I work there). It's built around Rust and not TS but we have some updates coming soon which is going to expand on this. We've been thinking about this DSL question for a while and it's pretty much a trade-off. By having your own language and parser you can build language primitives which get your close to your domain, as for example in the example you gave with HCL. It will be interesting to see where Wing goes with this concept, it could offer a great developer experience. For us, we've chosen to stick with a robust and performant programming language which is increasing in popularity and has enough meta-programming capabilities to make this 'infrastructure from code' paradigm feel natural - the framework blends in well with the language. The advantages of this for us is that users of the language experience a very small learning curve and they can also use incredible Rust libraries off-the-shelf. We can also piggy-back off the Rust compiler and ecosystem to provide an A-class developer experience (those compiler errors are amazing). We're excited to see more companies in this space - optimising for a beautiful developer experience.
- mikercampbell 4y agoI hecking love the concept of shuttle. The only thing keeping me from using it is unfamiliarity with rust, but it's enough to make me rethink things. I think the future isn't as much Lo-code as much as it will be (and goshdarn should be) Lo-DevOps. There are so many advances in programming, like WASM for example, that will continue to cause this Lo-DevOps movement, but honestly, digging into the language, using the stuff that already is baked in for other existing business purposes. But things like encore.dev and shuttle.rs (I'm associated with neither) are just mind-blowingly straightforward with no language, infrastructure, or other cognitively burdening information.
- zozbot234 4y ago> I hecking love the concept of shuttle. I'm not sure about it. If you're going to have Rust-specific deployment workflows, you should reuse the solutions that have been developed for the embedded ecosystem. There's no reason why "cargo flash" could not be extended to upload your binaries to the cloud, and support the same "probe run" workflow for remote logging and debugging.
- jchook 4y agoHCL in particular has so many annoying edge-case issues and limitations due to its immaturity that it becomes intractable beyond simple use cases. Thankfully Pulumi[0] allows me to write Terraform configuration in a language I know without reinventing the wheel. It feels like Pulumi's approach is better in every single way I can imagine. I simply do not see the reason for HCL whatsoever. [0] https://github.com/pulumi/pulumi https://github.com/pulumi/pulumi
- substation13 4y agoWhat about the non-determinism, lack of sand-boxing and Turing-completeness of a real programming language?
- jchook 4y agoWhat about the lack of a mature language server for code completion and at-your-fingertips documentation? What about the lack of mature tooling for static analysis, linting, code formatting, etc? What about the poor support for defaults and partial overrides on object-type (read: namespaced without redundant_underscore_thing_*) configuration directives? What about the very limited module capabilities? What about the limited set of deterministic functions available (e.g. you get base64, yaml, csv, and otherwise GLHF)?
- duped 4y agoThere's no reason the code can't be sandboxed, Turing-completeness is a feature not a bug (nor is undecidability a real problem), and non-deterministic behavior where it's undesirable is just a potential hazard in the real world. No system can avoid it unless that system never interacts with the outside world.
- newaccount2021 4y agoBecause those aren't real-world concerns??? HCL is its own language so Hashicorp can "own" the experience, tie you into an Enterprise toolchain, and scratch their "I've always wanted to build a language!" itch But it works and ops people love it because most ops people in industry today cannot even write a simple Python script. So...tools like Pulumi are actually out of their reach.
- no_wizard 4y agoIsn't that pulumi's angle? Its pure JS (well, written in TS and compiled to JS) that lets you leverage JS / TS for provisioning your infrastructure https://www.pulumi.com/ https://www.pulumi.com/
- nirga 4y agoNot exactly, Pulumi is more like CDK. So code and infra provisioning is still separate
- fishnchips 4y agoNot necessarily, at least in their JS SDK they have a clever way of actually compiling your Pulumi code directly into things like APIGW and handler Lambdas.
- deleted 4y ago[deleted]
- Garlef 4y agoIf I give you a function that I want you to deploy to a lambda. Can you do this with a pure JS library? No. Pulumi can do it but they have a compiler in the background. And you still need a lot of boilerplate devops stuff around it. So if you already need a compiler to do the packaging, etc. why stop there. A lot of other tooling problems go away. But yes, you'll be reinventing the wheel to some portion.
- OJFord 4y ago> If I give you a function that I want you to deploy to a lambda. Can you do this with a pure JS library? No. I'm not sure if you're making some distinction I'm not following, but yes? One of them is called 'AWS SDK for JavaScript'?
- nirga 4y agoNot exactly, cause you need to manage state or something (you don’t want to reprovision every time you run the code probably). So you’ll need to do some sort of “compilation”
- OJFord 4y agoHow does compilation remove the need to manage state? I'm not at all precious about JS, let's do it with the AWS SDK for C++ library instead?
- Garlef 4y agoSry. I should have been more explicit: Let's say you are writing JS and you have `const handler = ...` You can not do something like `const lambda = deployLambda(handler)` on the next line. Instead you need a deployment package. And to build this, you need to leave JS and involve some CI code and some IaC tool. But wing enables you to just do that. (seemingly, I've not tried it yet)
- ashiban 4y ago> Why is this a language, not just a framework for JavaScript or whatever? I'm one of the founders of Klotho (https://klo.dev https://klo.dev), and we're in the camp of expanding existing programming languages with cloud native building blocks. We’re building Klotho in that spirit. There's a few reasons to opt for using a compiler rather than SDKs: - Being able to catch errors as early in the development process as possible, rather than in runtime or production. - Being able to use existing language features and popular libraries. For example, we’re able to turn a standard Node.js EventEmitter into an asynchronous invocation on a different compute engine (basically, spinning off an AWS Lambda invocation or adding a message to an SQS queue). Not only does this reduce the barrier for entry, but it also often enables fast iteration time by supporting a local development workflow (no more waiting for deployments between changes). - Being able to trim the runtime to a minimal set that is necessary for that execution unit alone. In SDK land, you include the entire library, which means more lines of code to reason about in a live-site incident, alternatively going fully granular means developers now need to reason about what to include and what not to. Compilers, and specifically static analytics can reason about that automatically. - Being able to use all of that logic across languages: rather than having to write a separate SDK per language, we can write a single tool that works the same across multiple languages. In addition to aesthetic niceness, that could in the future let us handle polyglot code bases in a more cohesive way. We support JavaScript/TypeScript/Python, and are developing Golang/C# support
- awinter-py 4y agoalso terraform has a lot of ergonomic warts from being a language not an sdk -- for example: the minimum unit of reuse is a folder with a file in it, and loops and conditionals were impossible for a while pulumi is the 'terraform as a library' option, haven't tried but it makes sense
- mountainriver 4y agoYeah Pulumi makes a lot more sense than terraform and I find myself wildly more productive in it
- jacurtis 4y agoThese are some weak arguments against Terraform. > loops and conditionals were impossible for a while Yeah they were, in what version was it? 0.11 and 0.12 I think when those were added? But those have been there for a while. It was admittedly beta during the time and under active development. Regardless, its a moot point now, so not worth discussing. Still, conditional statements are limited to ternary style operators as opposed to complex multi-line if-statements. That would be a stronger argument to make that I could agree with. However, this was a design decision made by the team not a technical limitation. The goal is not to make complex logic decisions inside the declarative nature of Terraform since it takes you away from the declarative (documentation-style) markup that it stands for. Between using locals and modules and data sources you can still accomplish almost anything despite not having multi-line conditionals. The end result is cleaner, which is a design decision that was made. > the minimum unit of reuse is a folder with a file in it I don't really understand the problem with this. This is essentially how Go(lang) is too and other full blown languages. Its another design decision and not really a limitation. There are significant advantages to this, for example modules are folders and everything inside of them gets compressed into a single unit for replication purposes. Within that folder you can break your code up however you wish to improve readability and maintainability. This gives utmost flexibility to the author, and standardizes the consumption for the consumer. You can import a module and use it as a "packaged" unit without needing to understand how the author created it. These just sound like opinions you have more than "ergonomic warts". If anything I could argue that both of these design decisions of the language actually make it more ergonomic to use (and consume) not less. Its also worth noting that I mentioned multiple times authors/creators and consumers. Terraform is very much designed around being consumed and read, almost like documentation. If you talk to Hashicorp this is a huge motivation behind the DSL that is HCL. It was designed that someone who has minimal Terraform knowledge could use modules to create powerful infrastructure within a company. This is how we use it in our company. The SRE/Platform Engineers (where I work) build very advanced, complex, and powerful modules that are easy to consume with a handful of variables. We have developers that can spend a few hours learning Terraform and know enough to build production infrastructure within the company that is built to our design standards and security compliance requirements. They often don't even have to know what that is, they just declare a network, a database, and a cluster of compute with a handful of parameters that are auto-documented and they end up with some incredible infrastructure as a result. This is what Hashicorp is designing Terraform around. If you meet with them or go to their conferences, this is the direction and purpose of Terraform and how they designed it. A handful of Terraform experts at a company can create modules that are consumed by developers that have minimal knowledge of Infrastructure or Terraform. Its a powerful system.