Hacker News Reader

> The downside as an expert is realizing you have to get a PhD to get a sense for how much RAM your cats will gobble up.

Go one step further with affine types and use Rust. You get haskell type system with predictable performance.

View on HN

> You get haskell type system

No. When trying to use Rust's traits like Haskell you learn really fast why higher kinded types are needed.

Oh, wait, does Rust not have kinds? That's a bummer.

Rust has GAT's which have the same expressivity as HKT's. But many Haskell patterns turn out to be unidiomatic in Rust due to extra overhead. (For instance Rust has multiple function-like traits that access their environment differently. There's no equivalent to this in Haskell of course; GC and default boxing choices for Haskell types obviate the issue, but this is not zero cost.)

What is Rust missing out on?

I know, I know. It's very silly of me not to pick up Rust when I've already got all of its forbearers in my bones. Someday, once I've finished studying everything else I need.

Reply on news.ycombinator.com