Re:What part of Rust compilation is the bottleneck?
by davidmurdoch on Saturday March 16, 2024 @09:19AM
(#39725639)
I watch some intro to OCAML videos, got excited about the languages features, then tried reading some real OCAML (Tezos, which was touted as the star of idiomatic OCAML projects - can't find the site that listed it now), and I found it so incredibly dense, hard to read, and almost completely devoid of meaningful naming and comments. It felt similar to reverse-engineering minified code to me.
[ Parent
| on HN ]
Re:What part of Rust compilation is the bottleneck?
by whateveracct on Saturday March 16, 2024 @09:29AM
(#39725713)
sounds like unfamiliarity. OCaml isn't a language a layman can read without prerequisites.
Re:What part of Rust compilation is the bottleneck?
by davidmurdoch on Saturday March 16, 2024 @09:31AM
(#39725730)
I found the idea pleasant, but not in actuality. So maybe it's an acquired taste? Haha
Re:What part of Rust compilation is the bottleneck?
by whateveracct on Saturday March 16, 2024 @09:46AM
(#39725874)
oh it definitely is. A lot of Haskell can look like you describe, but it's perfectly legible if you have enough reps under your belt. I find normal languages hard to read nowadays.