<story><title>Announcing Go Support for AWS Lambda</title><url>https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/</url></story><parent_chain></parent_chain><comment><author>ramses0</author><text>What&amp;#x27;s the current state of the art for &amp;quot;I know I use AWS for my 9999-server production instance, but how can I test the majority of my services offline on an airplane w&amp;#x2F;o spending $199.99&amp;#x2F;mo to keep a fleet of test AWS servers&amp;#x2F;services at the ready&amp;quot;?&lt;p&gt;Last I looked the &amp;quot;fake-aws&amp;quot;, specifically &amp;quot;lambda&amp;quot; supported python, not JS&amp;#x2F;Node, which was not matching my use-case.  Go is now on the radar as a usable programming language for this purpose, but what are the chances of being able to also use it with local test deployments?</text></comment>
<story><title>Announcing Go Support for AWS Lambda</title><url>https://aws.amazon.com/blogs/compute/announcing-go-support-for-aws-lambda/</url></story><parent_chain></parent_chain><comment><author>Corrado</author><text>I guess I&amp;#x27;m confused as to how the support of one compiled language differs from any other compiled language; couldn&amp;#x27;t you just replace &amp;quot;Go&amp;quot; with &amp;quot;Rust&amp;quot; at this point?  I understand how Lambda would have to support scripting languages (NodeJS, Python, etc.) with built-in runtimes and such, but if you are going to compile down to a binary object anyway, why does it matter what language the binary object was written in?&lt;p&gt;Does it have to do with supporting libraries being pre-installed on the Lambda image or something?  Couldn&amp;#x27;t they build a Lambda image that handles any language that can interface to common &amp;quot;C&amp;quot; headers?</text></comment>