News for hackers. Stuff that matters.
Re:Comparing Go and Java, Part 2 – Performance by davidw on Tuesday September 18, 2012 @03:47PM (#4540111)
It'd be fun to throw Node.js and Erlang into the mix.
Re:Comparing Go and Java, Part 2 – Performance by dgv on Tuesday September 18, 2012 @04:52PM (#4540440)
You can see vs Erlang in http://shootout.alioth.debian.org/u64q/benchmark.php?test=al... and have a idea, Go is based on Newsqueak (lauched later of Erlang, other perspective to implement CSP).
Re:Comparing Go and Java, Part 2 – Performance by davidw on Tuesday September 18, 2012 @05:07PM (#4540516)
Sure, but this benchmark was more about concurrency, whereas those benchmarks are more generic. Erlang is not the fastest language out there, but it's supposed to be good at this concurrency stuff...
Re:Comparing Go and Java, Part 2 – Performance by igouy on Tuesday September 18, 2012 @05:23PM (#4540587)
Erlang is supposed to be good at distributed, reliable, soft real-time concurrent systems.

http://www.erlang.org/faq/introduction.html#id49480

Re:Comparing Go and Java, Part 2 – Performance by davidw on Tuesday September 18, 2012 @05:33PM (#4540637)
Somehow, it seems that when Erlang was getting a bit of hype, they abandoned the field for an even smaller niche, leaving the "real time web" type things to other languages. Granted, the language was created for that smaller niche, but if that's the only bit of terrain they want to defend... I see other languages squeezing them out over time.

I don't know if that makes sense, but languages need somewhat large communities to really thrive, in my opinion, and defining yourself into a small niche isn't a good way to get them.

Re:Comparing Go and Java, Part 2 – Performance by igouy on Wednesday September 19, 2012 @12:23PM (#4544211)
For a short time some people hyped Erlang to be the solution for all things concurrent and chatterers didn't read the FAQ.
Re:Comparing Go and Java, Part 2 – Performance by igouy on Tuesday September 18, 2012 @05:21PM (#4540575)
You chose not to compare against the faster Erlang HiPE measurements because...? ;-)