News for hackers. Stuff that matters.
Re:Why Elixir? A Rebuttal to Common Misconceptions by alternatex on Thursday July 24, 2025 @03:04AM (#44667809)
That's quite the list of languages. If you're interested in types I would suggest also looking into F#. Shouldn't be tricky for someone who has already experienced C# and is open to different approaches to programming. For me F# was a revelation into what programming language typing can do for the developer.
Re:Why Elixir? A Rebuttal to Common Misconceptions by Turskarama on Thursday July 24, 2025 @03:59AM (#44668178)
I really like the way F# (and presumably ocaml) do typing, it truly feels like the best of both worlds. Rarely do you need to actually write a type anywhere, and when you do it's because otherwise there might have been a runtime error.
Re:Why Elixir? A Rebuttal to Common Misconceptions by yxhuvud on Thursday July 24, 2025 @08:47AM (#44670001)
Sounds a bit like crystal. Flow typing etc is so powerful.
Re:Why Elixir? A Rebuttal to Common Misconceptions by iLemming on Thursday July 24, 2025 @01:23PM (#44673428)
I do know and like F#, and just like the other commenter I think I personally prefer it over some Haskell's ways. F# was my first FP language, I was so excited about it, but it was a hard sell back then to my team of charpers, so I sneaked it in by writing tests in it for an otherwise altogether C# codebase.

Too sad that the dotnet world largely still operates in csharpland and F# unfairly gets ignored even within dotnet community. I never have found a team where F# is preferred over other options, and I'd absolutely love to see what it's like. Unfortunately, F#'s hiring story is far worse than other less popular languages and even if there is anything, you most likely end up supporting other projects in C#, and honestly, even though it's a fine language by many measures, I see C# as "past experience" that I personally am not too eager to try again and do it as my daily job.