3 ms·

I am wondering if using some of the front-end techniques for back-end would be beneficial. Tree-shaking, minimization and gzip would probably help with the bina

I am wondering if using some of the front-end techniques for back-end would be beneficial. Tree-shaking, minimization and gzip would probably help with the binary file size. But as we go there, maybe some more advanced things like the closure[1] compiler or prepack[2] would make it faster. [1] http://www.syntaxsuccess.com/viewarticle/closure-compiler-vs-uglifyjs http://www.syntaxsuccess.com/viewarticle/closure-compiler-vs... [2] https://prepack.io/ https://prepack.io/

mbel 10y ago
> But as we go there, maybe some more advanced things like the closure[1] compiler or prepack[2] would make it faster. And then one could probably go even deeper in search of performance and instead of compiling JS to JS, compile it to C or even straight to native CPU assembly.
- andars 10y ago
  AOT compilation of js is probably not worthwhile.
douche 10y ago
Yeah. Like all those compilers and runtimes for the back-end languages we were already using before JavaScript ate everyone's brains, that served as the inspiration for all of this madness on the front-end side.
h1d 10y ago
Back end is about stability (= don't do fancy). So unless it increases performance like maybe prepack does, I don't see much point.