I agree. And isn't that exactly the solution the Serverless framework implemented?
I am not sure, but serverless requires more config and tweaking as compared to arhitect.
In contrast, serverless is a more mature and flexible platform.
It was more of a rhetorical question, Serverless definitely uses .yml
https://serverless.com/framework/docs/providers/aws/guide/se...
Obviously that's a verbose example and there are defaults for most everything AFAIK.
Anyway, Architect seems cool too! Always down for more options and competition!
Accepted, but that's not the topic of debate.
The issue here is that you can write the example you gave in YAML like this
And it could still generate the same result. But this way people can write the config in a more familiar syntax.Hope I explained my point correctly.
This is just a matter of UX/ API, not how it works.
If you somehow felt that I disrespected your work, forgive me.