Re:What technology should your startup use?
by _nato_ on Tuesday August 27, 2013 @04:03PM
(#6285901)
Is ``Jessica's'' comment not far from the truth because Scala and Go have shared memory for their Actors/Processes? I know Erlang doesn't share memory between their processes which leads to concurrency; is this what she was getting at?
In general (apart from run time code loading) one can accomplish a lot of things Erlang does in any language.
Her "how much pain and when" I think implies that she only accepts concurrency as practical when units of concurrency are isolated as that would reduce the number of shared data structures being updated, lock contentions and so on. There is some truth in there that I agree with.
But then again maybe she was just trolling. I for one do not like her tone her comment.
Re:What technology should your startup use?
by lucaspiller on Tuesday August 27, 2013 @04:17PM
(#6285990)
I haven't played around with Scala or Go, but it's not far from the truth in that Erlang is a pretty good bet.
Re:What technology should your startup use?
by blacktulip on Tuesday August 27, 2013 @04:04PM
(#6285905)
Thank you very much!
http://www.theerlangelist.com/2012/12/yet-another-introducti...
It is kind of like Node in that it is very easy to do concurrent stuff, except instead of nested callbacks and all that jazz, you write 'processes' which are designed to share nothing. They run akin to OS threads in that one process crashing won't bring down the whole system (unlike Node). As no state is shared it also means that they can easily (i.e. it is built into the VM, and switched on by default) be scaled up to run over many cores. If you are interested, you might want to look at Elixir (a language built on top of the Erlang VM) which has a more Ruby-esque syntax: http://elixir-lang.org/
EDIT: Should also point out that I think "Jessica's" comment was just trolling, however it isn't far from the truth :)