Bash Runtime for AWS Lambda
Yet another bash Lambda runtime, but the stdin/stdout contract is refreshingly simple.
A "wedge" to delegate tedious AWS Lambda I/O tasks and secure your API logic.
Cuts Lambda handler boilerplate in half, but Zappa and Chalice already exist.
AWS Lambda developers building API handlers
AWS Lambda Powertools · Chalice · Zappa
Lambda handlers often grow not because of business logic, but because of repetitive I/O glue code:
- event parsing - parameter validation - type casting - response formatting - error handling
slat-io isolates that I/O layer so handlers can stay small and focused on business logic.
It's intentionally tiny, dependency-free, and not a framework.
Still early, but I'd love feedback on the approach and API design.
Yet another bash Lambda runtime, but the stdin/stdout contract is refreshingly simple.
This is a concise dead-code-elimination pass implemented as ~140 LOC of readable Rust: it walks op dependencies via a match over Op variants, collects reachable OpRefs, and prunes the op pool. It’s not reinventing compiler theory, but the implementation is tidy and immediately pluggable into a small IR/dataflow project — useful as a reference or drop-in optimizer. Lacking benchmarks, docs on integration, or tests, it’s more of a pragmatic utility than a research contribution.
1.3MB C++ DSP library for Node.js Lambda beats SciPy's 90MB bloated package.
AgentForge packs provider adapters (Claude, GPT‑4, Gemini, Perplexity), token-aware rate limiting, retry/backoff, and a MockLLMClient for tests into a tiny dependency surface — the 15KB footprint and 2 dependencies is an attention-grabber. The 3‑tier Redis cache and benchmark claims (huge latency/memory wins vs LangChain, 88% cache hit) make it a tempting low-overhead alternative, though you should validate provider feature parity and benchmarks against your workload.
Yet another AWS SDK when boto3 v2 is already async-native and typed.
Hardcoded menu mapping breaks on price changes, but ordering burritos via pip is fun.