Re:Node.js Compiler – Compiling your Node.js application int...
by notsohuman on Friday May 05, 2017 @02:40AM
(#14271541)
I mean an actual compiler rather which is much more optimized than node environment rather than just making things into executables
[ Parent
| on HN ]
Re:Node.js Compiler – Compiling your Node.js application int...
by ComodoHacker on Friday May 05, 2017 @03:10AM
(#14271657)
V8 includes JIT compiler. Could it really be "much more" optimized?
Re:Node.js Compiler – Compiling your Node.js application int...
by perbu on Friday May 05, 2017 @03:35AM
(#14271743)
If you look at Hiphop vs. HHVM there is certainly a significant performance upside in taking advantage of clangs or gccs ability to produce efficient code.
I'm not sure why Facebook decided to stop maintaining hiphop. Perhaps manageability wasn't great.
Re:Node.js Compiler – Compiling your Node.js application int...
by mbel on Friday May 05, 2017 @03:31AM
(#14271724)
Perhaps. JIT compiler has to care deeply for compilation time. For AOT compiler compilation time is a little bit less pressing problem which leaves some space for optimization passes that take too long for JIT.
Re:Node.js Compiler – Compiling your Node.js application int...
by notsohuman on Friday May 05, 2017 @03:18AM
(#14271686)
I agree V8 does an awesome job buts it compilation phase is not done separate before running. Lot could done to gain the speed in those areas.
Re:Node.js Compiler – Compiling your Node.js application int...
by notsohuman on Friday May 05, 2017 @03:38AM
(#14271754)
there is always something more that can be done
Re:Node.js Compiler – Compiling your Node.js application int...
by perbu on Friday May 05, 2017 @03:31AM
(#14271723)
This would be pretty useful. Something like hiphop which could transpile into C or C++ would mean we (IncludeOS) could build tooling to run a node application on directly in a vm without a underlying OS.