SebastianVerified account

It's extremely slow and not scalable to really large apps.

We hope we can have enough time to devote to better concurrency and scalability enhancements. We'd love your help @sebmck

Also there is space for more than one packager with different goals in the world. Ideally they would share code (they kind of already do)

Of course there is. But fwiw, our goal is to be suitable for "large and scalable Sebastian apps" too.

As long as this is your complexity: https://twitter.com/wSokra/status/872353199818244096 … it's going to be impossible to make it work.

I'd be curious which parts need to be optimized/how to make it work. Speed via IPC/disk cache? Memory by TypeArrays/WASM/C++?

Complexity does not necessarily mean loss of speed /me stares at JS VMs

I meant more about the algorithmic complexity and amount of recursion. So much indirection there's very little places you can safely cache.