[pmarreck]

What's/where's your evidence?

1) The situation might have changed since you looked at this

2) The algorithm to do the work might have been suboptimal (for example, not taking advantage of pattern-matching, or using regex which everyone agrees is too slow in Erlang/Elixir)

3) for large files, there's some fiddly techniques that make things noticeably faster, see for example http://cloudless.studio/articles/12-elixir-vs-ruby-file-i-o-...

[dozzie]

1) It might, but I doubt BEAM got rewritten in that extent.

2) Split on a comma is very hard to get suboptimal, especially when it was `string' module supplied by Erlang.

3) Half of those fiddly techniques will be very, very hard to use in Erlang (I understand that the thread is about Elixir, so you sort of assumed that I was talking about it even though I explicitly said that it was Erlang and BEAM code). Then, the load was on the CPU, not I/O. Reading the file upfront was not going to help.

[pmarreck]

I don't know why you're getting downvoted just for dissenting. I don't want HN to be another damn Reddit echo chamber. Lots of criticisms of popular things are valid. I thought we were just having a civil discussion, but now I'm angry BECAUSE you got downvoted lol

But I would still like to see any evidence from you if you'd like