tadeegan

I used to work on this. Happy to answer questions.

Here is a good article about Closure Compiler optimizations which J2CL uses as its optimizing compiler: https://medium.com/@thomasdeegan/10-optimizations-closure-co...

This website has Closure Compiler compiled by J2CL running in the browser itself!

https://closure-compiler-debugger.appspot.com/j2cl_debugger....

This would be an interested DDOS attack for open source CI systems that check pull requests. Especially when combined with some sort of distributed network build cache like bazel, you could easily fill it the cache by making a few pull requests with this.

How does this compare to using XLA for AOT compilation?

nginx makes it very easy to sever multiple websites on a single ip.

As someone who works on Closure Compiler, this is one of my biggest gripes with the project. Things are getting better though! CC now supports node's module resolution algorithm. It works pretty well with Es6 imports but not so well with CommonJS (mostly because the exports are impossible to statically analyze).

Within Google, CC is heading towards being a an optimizing backend for other less painful languages such as Typescript (tsickle) and the yet-to-be-released J2CL compiler.

CC does pretty well with these examples (our debugger is not quite as flashy): https://closure-compiler-debugger.appspot.com/#input0%3D%252...

For portability and use within the node/npm ecosystem? Yes I think so.

This feels like the hacker news I remember. :)

This API seems... creepy.

When I looked into it, webtorrent still requires a centralized server to at the very least set up the peer to peer connection. The problem is that there isnt a way to avoid this with WebRTC. It also serves content to the initial peer.

How is this serverless? Am I missing something?

Kappa

Okay, seriously, what could someone possibly send over snapchat that is important to national security?