3 ms·
With the rush we forgot to update some of the cases in the product page, thanks for the feedback! We'll update them shortly. Right now we are starting with Rus
by syrusakbary 3y ago
With the rush we forgot to update some of the cases in the product page, thanks for the feedback! We'll update them shortly.
Right now we are starting with Rust (with full networking with tokio) and static sites.
Node.js (allowing Next.js to be fully runnable) and Python (allowing Django and Flask) support will be coming soon!
- ushakov 3y agoHow are interpreted languages possible in wasmer?
- syrusakbary 3y agoYou can compile the interpreter itself (such as CPython) to Wasm/WASIX and let Wasmer do it's thing :)
- ushakov 3y agoWhat about third-party modules? Next.js depends on SWC, which is written in Rust. Will it run on wasmer?
- syrusakbary 3y agoIt’s a technical challenge but we believe is fully doable. BTW, SWC is already powered by Wasmer!
- duped 3y agoHow is swc "powered by" wasmer?
- refulgentis 3y ago[dead]
- the_duke 3y agoSWC uses Wasmer for its plugin system to execute WASM plugins.
- eins1234 3y agoAlso curious about how Node.js support would work? I've heard about efforts to compile SpiderMonkey to WASM to run JS, but never V8 and the entirety of Node.js. That would be super exciting if that's what you're looking to accomplish. Would love to follow along and contribute if this is part of an open source effort! Curious if you think cold starts could be a problem with this approach? Share-nothing architecture sounds great until you realize you have to load the entirety of V8 and Node.js on every request, but maybe you've figured out some way to work around that? Also, how do you think the lack of JIT could affect real-world JS runtime performance? Or is there a solution for that too?