11–20 of 72 posts
I looked through the docs and I don't see any async methods, is that built into inflight like this code snippet I found? queue.setConsumer(inflight (body: str): str => { let next = counter.inc(); let key = "myfile-{next}.txt"; bucket.put(key, body); });
Can you explain the idea behind a cloud-oriented programming language? How does it works?
I'm not affiliated, but I'd guess that things like "object storage" are a first class citizen, similar to a "string" or "float" in other languages.
I looked through the docs and I don't see any async methods, is that built into inflight like this code snippet I found? queue.setConsumer(inflight (body: str): str => { let next = counter.inc(); let key = "myfile-{next}.txt"; bucket.put(key, body); });
Yap, all inflight code is async by default.
Very cool! What's the difference between WinLang and Serverless?
The way I read it is that Winglang combines your IaC and your runtime logic/code. In theory it's pretty neat, I haven't given it a serious try though. I'm not totally convinced that I want my infrastructure definition intermingled with my business logic though.
Very cool! What's the difference between WinLang and Serverless?
> infrastructure and runtime code in one language This is fertile ground for new languages, apparently they call this the "Construct Programming Model" but there appears to be no meat to the theory. If programming language theory was leveraged properly I think they'd really be on to something. See the success of Rust for example. I just did some cursory research and came across a paper on "ABS: A high-level modeling…
I will read the article you mentioned, sounds interesting
Given this language is really about abstracting network calls to external services as objects/methods wouldn't it make sense to have return values be maybes and then be able to pattern match on that given that these are not local calls and networks/services do fail?
My guess is an actor pattern where you are sending messages to these services and waiting for responses instead of faking a local call would surface the error conditions in a much cleaner way, ala Erlang or Elixir.
This may be helpful: https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...
I've used CF, and TF and was an early adopter of CDK. I'm curious how this compares with Pulumi (never tried it). I liked the idea behind CDK but was shy about going all in because it was AWS-specific. Looks like this is the natural progression.