Compilation warnings shouldn’t exist; a compiler should only build your program, and fail only when it can’t produce it’s output; a linter’s job is to raise warnings

Modren languages should come with batteries included; complete build system, dependency management, a package index.
A formatter, linter & documentation generator are also nice to have.

Monolith is very hard to work with in the long run; Separate your project into reasonable, small repos, each having a straightforward development and deployment strategy

I’m building USM - The Universal Assembly; an LLVM IR competitor, that has a single, united, low level assembly syntax, compiles to modern backends, and implements generic and backend specific optimizations.

v0.1.0 expected to release in < 6 months.

github.com/RealA10N/usm

Golang has the best balance between performance and productivity

There are no advantages for interpreted languages in production

My 2025 Python stack;

build system: uv / hatchling
formatter, linter: ruff
static type checking: mypy
input validation & data-classes: pydantic

Zig’s comptime is superb, but not perfect; An ideal comptime implementation should not use additional syntax.

www.scottredig.com/blog/bonkers...

שלום בלוסקיי 🤘