nerd

Rails/Ruby performance has improved: https://medium.com/retention-science/ruby-is-still-a-diamond... Alhough, compiling Javascript to binary makes code even faster https://nectar.js.org , although I wish that project would get more love with bugfixes https://github.com/NectarJS/nectarjs/issues

Hi all, NectarJS is becoming more mature every day : the memory is managed in real time without garbage collector and the performance are good. To demonstrate what we can do, Wesley (from Discord) created some neural networks examples. The 4096 x 4096 nn example gives a JavaScript heap out of memory with NodeJS, but compiles and run fine with NectarJS : https://i.imgur.com/4BjDAgM.jpg You can find the code here: https://github.com/NectarJS/nectarjs/blob/master/example/nn4096.js Right now, NectarJS supports most of ES3, but we need help to improve NectarJS and make it better: - Improve the std libs - Libuv integration for NodeJS support (started with fs.readFile as a POC and working fine) - Custom parser to self compile NectarJS - Supporting fully ES3, ES5, ES6 ... NectarJS is fully open source, so don't hesitate to join us on Discord (htt

I wonder why people still try write transpiler from JS to C/C++ or LLVM (which make sense at least). But this not performant way and usually produce much bigger overhead than jit vm which use speculative optimizations. Some projects: 1. https://github.com/fabiosantoscode/js2cpp 2. https://github.com/raphamorim/js2c 3. https://github.com/ammer/js2c 4. https://github.com/NectarJS/nectarjs 5. https://github.com/ovr/StaticScript

https://github.com/NectarJS/nectarjs Still not sure if it's just a 'cool hack' or an attempt at a serious product though.

Takeaway from a previous discussion: https://news.ycombinator.com/item?id=13938832 (36 points, 1 day ago, 28 comments) About the benchmark: > That the C code is compiled with "gcc -O7" tells me just about everything I need to know about the soundness of these experiments. [...] About the alpha test: * It's weird that they disable the alpha https://github.com/seraum/nectarjs/issues/1 * It failed to compile some code, like var hello = {foo: "Hello, world!"}; console.log(hello["foo"]);

More importantly, that source-code isn't the compiler - it just makes calls to the server that runs the compiler: https://github.com/seraum/nectarjs/blob/master/nectar.js#L52.... We don't even get to see how the compiler works, much less use it to debug when things go wrong.

Everything looks like a scam, see that one, for example, https://github.com/seraum/nectarjs/issues/1 ... and it's getting worse if you dive deep in the source code...