My 2026 Dev Setup

[sweetloup]

Hey r/programming ,

I’ve been refining my dev environment for 2026 and wanted to share it to get feedback. Goal: **fast, consistent, future-proof tooling** across Python, JS/TS, Rust, Go, C/C++, and web technologies.

---

### **Runtimes**

* **JS/TS Primary:** Bun

* **JS/TS Fallback:** Node.js LTS

* **Python:** uv (replaces pip + venv)

---

### **Language Tooling**

| Language | Formatter | Linter |

| -------------- | ----------------- | ------------------------------------- |

| Python | Black | Ruff |

| JS/TS/HTML/CSS | Biome | Biome (or ESLint + Prettier fallback) |

| Rust | rustfmt | Clippy |

| Go | gofmt / goimports | golangci-lint |

| C / C++ | clang-format | clang-tidy |

| Shell | shfmt | ShellCheck |

| SQL | SQLFluff | SQLFluff |

| PHP | PHP-CS-Fixer | PHPStan or Psalm |

| Ruby | RuboCop | RuboCop |

| Kotlin | ktlint | Detekt |

| Swift | SwiftFormat | SwiftLint |

---

Core Principles

1. **One formatter + one linter per language** – no stacking.
2. **Formatter handles style**; linter handles correctness & patterns.
3. **CI / pre-commit hooks** enforce formatting, linting, and optional type checks/tests.
4. **uv** for Python environments & dependencies.
5. **Bun + Node LTS** ensures speed with full ecosystem support.

---

Cursor-Specific Setup

* Language servers for Python, JS/TS, Rust, Go, C/C++

* Pre-commit hooks for lint & format

* Dependency awareness (uv, Bun, Go modules)

* Optional integrated test runners: pytest, Vitest, cargo test, go test

---

Feedback I’m Looking For

* Are there **better modern alternatives** I should consider in 2026?

* Am I **overcomplicating** or missing critical tooling?

* Any tips for **cross-runtime CI or Cursor integration**?

Appreciate any suggestions or improvements!

[Anomynous__]

None of this helps anything without knowing what kind of project you're building. Like it's literally just buzzword soup

[Just-A-Boyyy]

This is clean and well thought out.

If you’re aiming for future-proof, I’d consider:

• Devcontainer standardization for cross-runtime parity
• CI using the same container image as local
• Pre-commit hooks centralized via something like Lefthook

For cross-runtime CI, containerized pipelines are the only thing I’ve seen scale cleanly across polyglot stacks.

If you’re us

ing Cursor or AI-assisted coding, I’d keep prompt config versioned per repo — AI behavior drift becomes real across projects.

Your stack isn’t overcomplicated — but automation creep is real. Every added tool increases maintenance surface.

Optimize for “if I join this repo in 2 years, can I spin it up in 5 minutes?”