ekeren

Cloud Formation (https://aws.amazon.com/cloudformation/)

Disclaimer, I work at Monada, the company behind wing

I completely agree with you, a language that considers cloud development as a first class citizen must embrace something like open-telemetry for distributed logging (spans, traces, metrics, logs). When you log something or measure something in your code it should always be part of some distributed trace. We want to embrace this thinking for localhost development and allow our customer to choose their APM provider when they deploy. In a sense we don't see a difference between a cloud resource that is called logger (can be implemented by DataDog, New Relic, Coralogix, etc) and a cloud resource that is called a Queue (can be implemented by SQS, Redis, RabbitMq, etc...)

Also, as you mentioned, because in practice all the `inflight` (https://docs.winglang.io/concepts/inflights) code is async by nature, the language should wait for any API call to be resolved (e.g. "await") by default, deferring an API call is the exception

This is exactly what we are referring to in the suggestion

You are correct, you can commit it again

It is exciting, the language is full of modern stuff... This is what I catch at a glance of the book:

- Optionals (Java's @Nullable)

- Tupples

- Functions as first class citizens

- let vs var (immutable vs mutable)

- Operators are functions

- Closures

- Extensions (Adding things to an existing class)

- Value object (struct - are passed by value -- and so are Strings!!! )

- Reference Objects (class)

- Generics (lets hope it will be better than Java's version)

- External Parameters ??

- @final keyword (to prevent overrides - like Java's final)

It kinda looks like C# meets Ruby meets the let keyword Very complex...

And More

- object reference operator === and !==

- typealias (~ typdef)

- Optional Binding (if let x = y.f() { } else {}

- for-in loops (for i in 0...count)

- The default behavior of switch is not to fallthrough

Funny