[01HNNWZ0MV43FF]

It would be cool to see a linter, or a new language, that makes good architecture easy and bad architecture hard.

Like making state machines easier than channels. (Rust is sort-of good at state machines compared to C++ but it has one huge issue because of the ownership model, which makes good SMs a little clumsy)

Or making it slightly inconvenient to do I/O buried in the middle of business logic.

[skydhash]

Bad architecture is a communication problem, not a technical one. It’s rushing in without knowing the domain and its constraints.

Doing IO in the middle of business logic is just bad coding. It’s usually the developer not caring about the architecture (tornado coding or slum coding) or the architecture not existing.

[striking]

The language is English, the linter is us. These are things ultimately solved by establishing good processes and frameworks, making it difficult to do a task in a way other than the intended one.

[stereolambda]

Functional programming languages (OCaml, Clojure, Haskell), are supposed to be somewhat like this.