syrusakbary

6 ms·

31.
by syrusakbary 7mo ago
> I could not find usage examples on the edgejs.org page and the docs link points to the node docs, why? This was intentional, as a demonstration that Edge and Node should not diverge a bit. You should be able to replace `node` with `ed
32.
by syrusakbary 7mo ago
Yes, it could run in iOS (using JavascriptCore, V8 in jitless mode, or QuickJS), although we don't have a prototype app yet. It should probably take a few hours with AI to get a demo for it :)
33.
by syrusakbary 7mo ago
Edge.js is fully compatible with Next.js
34.
by syrusakbary 7mo ago
Since when we accepted that we can’t go fast and offer stability at the same time? Time is highly correlated with expertise. When you don’t have expertise, you may go fast at expense of stability because you lack the experience to make good
35.
by syrusakbary 7mo ago
It’s not a dumb question at all. And yes, it will allow running Node.js apps fully on the browser, in a way that’s more compatible than any other alternative! Stay tuned!
36.
by syrusakbary 7mo ago
We are so deep into the weeds that sometimes is hard for us to realize that maybe we are not explaining in the best terms. What was the most confusing thing in the blogpost? I'd like to polish a bit more to make it clearer! Thanks a lo
37.
by syrusakbary 7mo ago
Only the current working directory will be exposed/mounted to the runtime (we do this to facilitate the DX when running local files without requiring the user to add extra flags). As a fun exercise, you can try reading process.cwd() fr
38.
by syrusakbary 7mo ago
Hi HN! I'm Syrus, from Wasmer. We built Edge.js in a few weeks after different trials trying to bring Node.js to the Edge. We used AI and Codex heavily for this project, as otherwise the timeline would have spanned to a year plus to de
39.
by syrusakbary 7mo ago
Fully disagree with this take. Not allowing AI assistance on PRs will likely decimate the project in the future, as it will not allow fast iteration speeds compared to other alternatives. Note aside, OpenJS executive director mentioned it&#
40.
Edge.js: Run Node apps inside a WebAssembly sandbox(wasmer.io)
173 points by syrusakbary 7mo ago|45 comments
41.
by syrusakbary 8mo ago
Not right now but we would love to provide it. We have been super busy lately, but when we have a chance we will work on it!
42.
by syrusakbary 8mo ago
I also disagree with that. Wasmer can run now Python server-side without any restrictions (including gevent, SQLAlchemy and native modules!) [1] [2] Also, cool things are coming on the JS land running on Wasmer :) [1] https://was
43.
by syrusakbary 8mo ago
This is amazing. At Wasmer we are a bit concerned of Next.js and this replacement might come in handy! I actually was thinking on creating something similar. Congrats to the Cloudflare team
44.
by syrusakbary 8mo ago
This is super cool!
45.
by syrusakbary 8mo ago
Hi HN! I'm super excited about this release. We have been working hard on the last months to enable Python greenlets in WebAssembly. Happy to answer any questions!
46.
Greenlet Support for Python in WebAssembly(wasmer.io)
4 points by syrusakbary 8mo ago|1 comments
47.
by syrusakbary 9mo ago
Thanks for the ping, it seems our website got wrongly flagged. We are now chatting with the security providers to solve it. We'll re-submit soon once this is solved :)
48.
by syrusakbary 9mo ago
Might be worth taking a look at WASIX [1] We implemented all the system calls necessary to make networking work (within Wasm), and dynamic linking (so you could import and run pydantic, numpy, gevent and more!) [1] https://wasix.
49.
by syrusakbary 9mo ago
Nice! Fork is actually already working on Wasmer thanks to WASIX :) (and sockets, subprocesses, ...). Let me know if you need any help using it!
50.
by syrusakbary 9mo ago
Browserpod is great, been following it for a bit. Keep the good work up! The main issue that I see with Browserpod is very similar to Emscripten: it's designed to work mainly in the browser, and not outside. In my view, where Wasm real
51.
by syrusakbary 9mo ago
> For agent tool calling, you don't really need NumPy and Pandas. That's true, but you'll likely need sockets, pydantic or SQLAlchemy (all of of them require heavy support on the Wasm layer!)
52.
by syrusakbary 9mo ago
This is great! While I think that with their current choice for the runtime will hit some limitations (aka: not really full Python support, partial JS support), I strongly believe using Wasm for sandboxing is the way for the future of conta
53.
by syrusakbary 9mo ago
With Wasmer you should be able to use all pypi packages (even the native ones), although we are a bit light on the native packages we support now
54.
by syrusakbary 9mo ago
Stay tuned, we are about to release a new version of Wasmer with WASIX, that allows for things that can't currently be done with Pyodide: * Multithreaded support * Calling subprocesses * Signals * Full networking support *
55.
WebAssembly Clouds: The World After Containers(wasmer.io)
4 points by syrusakbary 9mo ago|0 comments
56.
by syrusakbary 9mo ago
> you can't implement a JIT compiler that targets WebAssembly in a sandbox running in WebAssembly That's not completely true. With dynamic linking (now supported in WASIX), you can generate and link Wasm modules at runtime easi
57.
by syrusakbary 9mo ago
WASI in their first attempt has been a success (what now is called wasip1). wasip2, p3, are tied into the component model. I'd say that wasip1 has been successful, but not any future version. You can check which version is the most pop
58.
by syrusakbary 9mo ago
Great analysis. I'm Syrus, from Wasmer, and I've been working on WebAssembly professionally for the last 7 years (we are, in fact, the first Wasm-first company!)... hopefully my point of view would be useful to read! Why things ar
59.
by syrusakbary 10mo ago
I'm building two things (that I expect to fully be done within a week or two!) * Go runnable in WebAssembly and WASIX * Node.js fully runnable in WebAssembly and WASIX Already had a prototype of one! ;)
60.
by syrusakbary 10mo ago
Completely agree on this. Regarding cold-starts, I strongly believe V8 snapshots are perhaps not the best way to achieve fast cold starts with Python (they may be if you are tied to using V8, though!), and will have wide side effects if you

More ›