I wrote a thing about how I switched from #haskell to #rust as my primary language.
https://blog.clement.delafargue.name/posts/2024-10-14-oxydizing-my-curry-one-year-later.html
@clementd Did kind of the same. After 6 yrs of #haskell I switched the job and introduced rust there. Company builds packing machines. So it was to introduce PLC programmers to a new language - haskell would have been probably too much.
Also still missing things (f.e. GADTs). But on the other hand f.e. associated types do their job as type functions (type families) which is great. Private toy projects also with a "cargo init" instead of "cabal init" in the meantime.
@alios Yeah, associated types come in handy, but I hardly went as far with them as I went with tyfams
@clementd tend to use typenum and uom crates quiet a lot. Imo good examples of typelevel coding in rust.
@alios I wonder if there is an equivalent of symbols. They regularly came in handy in Haskell
@clementd "I still think #Rust’s adoption is not aligned with the level of abstraction it promotes, and that most programs would benefit from higher-level languages, but most of the high-level languages are so bad that Rust is still comparatively great as a high-level programming language, just because it’s such a good language."
Heh.
@janriemer @alcinnz It's been good so far