> Isn't the library too old? If it works, it works. The library is pretty small anyway, you can probably roll your own.
> And I think the SSL thing is a bit of a hassle. When you do the custom runtime approach, you have to package every dependency your application requires. If you take a look at the AWS C++ lambda example's repo, they tell you about [this](https://github.com/awslabs/aws-lambda-cpp?tab=readme-ov-file#packaging-abi-gnu-c-library-oh-my). It's honestly not that hard to use Nimscript to run `ldd`, copy the libraries into a packaging directory, and zip it. (Just be careful with calls to `dlopen`; AWS warns about this too.) It accomplishes a similar thing AWS is doing in their repo. > I was thinking of using it at work. I don't want the dev coming after me to > be in trouble. I'm not going to say too much here, but I have successfully deployed an application written in Nim on AWS Lambda at work. It really isn't too much hassle. Once you've gotten the boring bits of packaging out of the way, it's really easy to build and deploy applications using Nim.
