News for hackers. Stuff that matters.

A comment on The Cloud is dead, long live the Cloud Announcing Wasmer Edge. Parent comment

Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by syrusakbary on Thursday June 15, 2023 @02:55PM (#36344992)
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!

[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by ushakov on Thursday June 15, 2023 @03:02PM (#36345044)
How are interpreted languages possible in wasmer?
[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by syrusakbary on Thursday June 15, 2023 @03:04PM (#36345064)
You can compile the interpreter itself (such as CPython) to Wasm/WASIX and let Wasmer do it's thing :)
[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by ushakov on Thursday June 15, 2023 @03:07PM (#36345091)
What about third-party modules? Next.js depends on SWC, which is written in Rust. Will it run on wasmer?
[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by syrusakbary on Thursday June 15, 2023 @03:09PM (#36345116)
It’s a technical challenge but we believe is fully doable.

BTW, SWC is already powered by Wasmer!

[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by duped on Thursday June 15, 2023 @03:47PM (#36345529)
How is swc "powered by" wasmer?
[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by the_duke on Thursday June 15, 2023 @04:09PM (#36345809)
SWC uses Wasmer for its plugin system to execute WASM plugins.
[ Parent | on HN ]
Re:The Cloud is dead, long live the Cloud Announcing Wasmer ... by eins1234 on Thursday June 15, 2023 @05:25PM (#36346706)
Also 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!

Also 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?

[ Parent | on HN ]