> I'd prefer to not have integration with proprietary commercial software as > part of the standard library.
That's a reasonable concern for sure. Still, until the cloud providers find Nim important enough to ship their own SDKs, this is a MAJOR use case in the real world, and will be a real impediment in to adoption in a lot of tech companies, if it's not easy to find something that works well and is clearly around for long-term support. Perhaps that suggests having another "ring" of modules that aren't shipped with Nim, but are officially maintained via the foundation.
