I originally built Flint for myself to get rid of the slow edit-deploy-test loop when working with Go AWS Lambdas, but thought others here might find it useful.
Flint uses a custom runtime inside your Lambda that pulls cross-compiled binaries from an S3 bucket on the fly. When you save a file locally, Flint automatically recompiles and uploads the new binary, letting the Lambda hot-swap the running process instantly without triggering cold starts or waiting on pipelines.
vaijab•1h ago
Flint uses a custom runtime inside your Lambda that pulls cross-compiled binaries from an S3 bucket on the fly. When you save a file locally, Flint automatically recompiles and uploads the new binary, letting the Lambda hot-swap the running process instantly without triggering cold starts or waiting on pipelines.