News for hackers. Stuff that matters.
Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by gogodancer on Friday December 30, 2016 @08:49PM (#13288956)
About V8 JavaScript: "Slow, because compared to C, Crystal or Go, it's slow."

In my experience writing real world server programs, Node.js is faster than Go in many cases. Part of this is a lack of Go library maturity, but it's also due to the fact that V8 optimizes code at runtime based on how it's being used. This project seems to come from a naive, "interpreted slow, compiled fast" view of the world, leading to false assumptions like Go is going to be automatically faster than Node.js because Go is AOT compiled and Node is JIT compiled.

Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by geocar on Saturday December 31, 2016 @03:38AM (#13290176)
I can't speak to Go or Crystal. V8 performs well on microbenchmarks, but very poorly with a sustained high volume of input due to GC pressure. I've used node.js in such an application and "version 2" was written in another language because of the GC pauses.
Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by gogodancer on Sunday January 01, 2017 @04:33AM (#13295232)
So what was the language C, C++, Rust?
Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by geocar on Sunday January 01, 2017 @02:44PM (#13296948)
KDB, although I'm experimenting with Erlang for some things and it seems sufficient.
Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by danielearwicker on Tuesday January 03, 2017 @04:07AM (#13307872)
Odd. Erlang uses GC.
Re:Nectar: A Native JavaScript Compiler Inspired by Crystal ... by geocar on Tuesday January 03, 2017 @05:11PM (#13313624)
Yes, but many small heaps means small GC pauses. It's not as deterministically/fast as reference counting (KDB) but it's close.