Why Elixir? A Rebuttal to Common Misconceptions

Re:Why Elixir? A Rebuttal to Common Misconceptions by kstrauser on Thursday July 24, 2025 @01:47AM (#44667343)

Not directly, it wasn’t:

  >>> open('foo') * 3
  Traceback (most recent call last):
    File "<stdin>", line 1, in <module>
  TypeError: unsupported operand type(s) for *: '_io.TextIOWrapper' and 'int'

You have to go to some length to get Python to mix types so badly.

[ Parent | on HN ]

Re:Why Elixir? A Rebuttal to Common Misconceptions by Orygin on Thursday July 24, 2025 @03:39AM (#44668026)

Won't prevent you from shipping this in prod. The stack trace you shown only appearing when you execute the code.

[ Parent | on HN ]

Re:Why Elixir? A Rebuttal to Common Misconceptions by cess11 on Thursday July 24, 2025 @06:11AM (#44668980)

Tests will, however.

[ Parent | on HN ]

Re:Why Elixir? A Rebuttal to Common Misconceptions by Orygin on Thursday July 24, 2025 @06:26AM (#44669058)

Sure but that's not what we were talking about. Plus I don't need to add tests like this in my code for it to be valid once compiled

[ Parent | on HN ]

Re:Why Elixir? A Rebuttal to Common Misconceptions by kstrauser on Thursday July 24, 2025 @09:56AM (#44670730)

Or run mypy etc., because you care about your code.

[ Parent | on HN ]