Earlier quoted context omitted.
[I'm on the Wing team] Wing is still in early days so we can't show very complex use cases yet, but as time passes developer use to build more and more complex things with it. Our aim is to improve productivity and speed by enabling developers to develop against a local simulator and visualization console, giving them instant feedback and much shorter iteration cycles. By allowing them to work at a higher abstraction…
> dev against a local simulator But can’t you already do this today with GCP and AWS and more generally a wealth of Docker images and Kub/Knative? Furthermore, I wonder how you guys plan to encourage users to jump ship from (node/go/Java/.NET) to winglang, all of which have a rich package ecosystem?
not really.. as soon as you need cloud resources that are not in your k8s cluster, you end up with the cloud in your development loop.
> what about the package ecosystem?
wing has interoperability with the npm ecosystem, so basically any node package can be used quite easily from winglang code.
on the infra side, there’s interoperability with the CDK for terraform ecosystem.