Great to hear that. I actually think TypeScript is very fit for the purpose, even better than Python (lacks types) or Java (bulkier).<p>Type signatures document contracts directly:<p><pre><code> export function rabinKarp(text: string, pattern: string): number[]
</code></pre>
Clear that it takes two strings and returns match positions. No separate explanation needed.<p>Interfaces model return types and ADTs cleanly:<p><pre><code> export interface ShortestPathResult<T> {
dist: Map<T, number>;
parent: Map<T, T | undefined>;
}
export function dijkstra<T>(graph: Graph<T>, source: T): ShortestPathResult<T>
</code></pre>
It's also lightweight, flexible, has familiar C-like syntax, and unlike pseudocode — you can actually run everything.<p>Re: generics feeling awkward — in TypeScript they feel pretty natural. The type inference helps a lot, you rarely need to spell out type parameters at call sites.