I was wrong about Typescript, part 1

A developer who previously worked with Rust found TypeScript problematic due to fundamental weaknesses that undermine its type safety promises. The language lacks concrete error return types, forcing developers to guess when functions might throw exceptions, while the "any" type allows bypassing type checking entirely by casting incompatible types. Unlike Rust's compiler-enforced guarantees, TypeScript's structural type system exists only at compile time and cannot verify that functions actually implement their declared signatures, making it feel more like enhanced documentation than true type safety.