📎 Webclip
What's your go-to stack these days?
The post asks what people would pick for their usual work if they had to start a new project and still deliver on time and on budget. The comments collect preferred stacks for different kinds of work, from Rust and TypeScript to Laravel, React, Kotlin, and serverless options.
Reading notes#
- The prompt asks what toolchain someone would reach for for typical work, not for a special project.
- One reply names Rust plus TypeScript, and says the pair balances Rust’s strictness with TypeScript’s speed for prototyping.
- Another reply lists Actix Web on the Rust side and XState with lit-html or lit-element on the front end.
- Several comments discuss hosting and deployment choices for Rust, including AWS Lightsail and Lambda.
- A Go setup appears as Go, Lambda, and DynamoDB.
- Another common stack in the thread is TypeScript, React or Next.js, PostgreSQL, Nexus, and Prisma.
- One reply says Laravel on the back end with React on the front end, plus Postgres and Redis.
- Another comment says Laravel’s default front-end toolset uses Vue, but React can be used too.
- A different reply prefers Ruby, Rails, Postgres, and Vanilla JS when the goal is to deliver on time.
- One comment says Kotlin across the whole stack, with Ktor for server-side apps and MPP for sharing models and logic.
- One response describes a regulated hardware environment where the stack includes firmware, VxWorks, ASP.Net MVC, Signal R, and Vue.
- Some comments also mention FastAPI, Django, and using tools like VS Code, Markdown, and Google Docs for writing.
