News for hackers. Stuff that matters.
Re:Erlang is a hoarder by damienkatz on Monday February 13, 2012 @03:51PM (#3587289)
Uhh, I've seen this too. Part of the reason we are migrating some code from Erlang to C.
Re:Erlang is a hoarder by dizzyd on Monday February 13, 2012 @07:05PM (#3587955)
It could be argued that this is a poor reason to switch from Erlang to C -- this is a problem with how binaries are handled in user code, not something intrinsic to Erlang VM.
Re:Erlang is a hoarder by anthonyb on Monday February 13, 2012 @07:18PM (#3587994)
It could also be argued that you will still have memory problems, just of a different type :)
Re:Erlang is a hoarder by Saavedro on Tuesday February 14, 2012 @02:19AM (#3589017)
Eh, every factor involved is implementation detail. The threshold at which binaries are heap-alloc'ed, gc behavior, etc. I really fail to see how this is user error.
Re:Erlang is a hoarder by frooby on Tuesday February 14, 2012 @03:52AM (#3589218)
I really fail to see how this is user error.

That isn't what the parent comment said.

Re:Erlang is a hoarder by itaborai83 on Monday February 13, 2012 @07:39PM (#3588054)
what parts? I'm interested about the future of Couch(Base|DB) sans all the Apache wankery.

I really wish you'd take more of a BDFL approach to things.

Re:Erlang is a hoarder by jchrisa on Monday February 13, 2012 @11:20PM (#3588590)
Specifically we're working to get Erlang out of the data path. So the code where throughput and latency really matter is written by hand and compiles directly to machine code, and Erlang continues to do what it does best - manage distributed systems and asynchronous processes.

In theory a great VM could out-perform C, but after you've chased down a few Erlang VM WTFs, there's something nice about being closer to the metal.