HackerTrans
TopNewTrendsCommentsPastAskShowJobs

syrusakbary

5,988 karmajoined 13 tahun yang lalu
Mathematician. Creative. Entrepreneur. Wasmer Founder & CEO. GraphQL/Graphene-Python creator.

https://wasmer.io/

https://x.com/syrusakbary

Submissions

Porting Wasmer Django backend to Rust improved the infra usage by 90%

wasmer.io
2 points·by syrusakbary·bulan lalu·0 comments

Nanobrew: The fastest macOS package manager compatible with brew

nanobrew.trilok.ai
225 points·by syrusakbary·4 bulan yang lalu·146 comments

Edge.js: Run Node apps inside a WebAssembly sandbox

wasmer.io
173 points·by syrusakbary·4 bulan yang lalu·45 comments

Greenlet Support for Python in WebAssembly

wasmer.io
4 points·by syrusakbary·5 bulan yang lalu·1 comments

WebAssembly Clouds: The World After Containers

wasmer.io
4 points·by syrusakbary·6 bulan yang lalu·0 comments

Beyond the SQLite single-writer limitation with concurrent writes

turso.tech
80 points·by syrusakbary·9 bulan yang lalu·70 comments

Series-A Documents – streamline the fundraising process

standardcap.com
1 points·by syrusakbary·10 bulan yang lalu·0 comments

comments

syrusakbary
·17 jam yang lalu·discuss
It's refreshing to see more self-made JS runtimes.

I'd love to see if I can integrate it onto Edge.js for full Node.js support ( https://edgejs.org )
syrusakbary
·5 hari yang lalu·discuss
Fixed!
syrusakbary
·10 hari yang lalu·discuss
Yeah, we create Wasm Containers from your application and deploy it to the edge so it can scale serverlessly :)
syrusakbary
·11 hari yang lalu·discuss
Excited on what this brings to the server-side :)
syrusakbary
·20 hari yang lalu·discuss
We have created Edge.js that can run Node.js apps fully using your preferred JS runtime: V8 or QuickJS.

https://edgejs.org/
syrusakbary
·30 hari yang lalu·discuss
If you are looking for a Systems Interface, I don't think the Component Model will be a good fit
syrusakbary
·bulan lalu·discuss
Congrats on the release to the WASI team.

TL;DR: WASI 0.3.0 is the Component Model-based WASI proposal. It adds async/await-style capabilities such as actors and streams, and today is runnable in only one server-side Wasm runtime (it is not supported natively by browsers). Unfortunately it still breaks compatibility with the original WASI proposal and runtimes that supported it.

If your goal is to compile existing, unmodified C/C++ programs and libraries to WebAssembly, WASIX may be a more practical option today ( https://wasix.org/ ). Disclosure: I’m part of Wasmer, the company behind WASIX.
syrusakbary
·bulan lalu·discuss
This is a fork of Chicory, a bit more context of the relationship between the projects can be found here:

https://github.com/dylibso/chicory/issues/1296
syrusakbary
·2 bulan yang lalu·discuss
It's great to see that since the release of Edge.js [1], they started to take Node.js compatibility more seriously (they went from ~40% to about 75% in just 2 months, so either coincidental or not this is clearly a step on the right direction).

Good work to everyone on the Deno team!

[1] https://edgejs.org/
syrusakbary
·3 bulan yang lalu·discuss
Yeah, the strategy is literally the same
syrusakbary
·3 bulan yang lalu·discuss
Wasmer (YC S19) | https://wasmer.io/ | Multiple Roles | Remote (EU) or Office (US) | Full-time

We are building the next generation of infrastructure for AI without Docker containers, but with a better container technology based on WebAssembly!

We are hiring for:

  * Rust Engineer (Remote, EU timezone)
  * Rust Distributed Engineer (Remote, EU timezone)
  * Developer Education Engineer (Office, San Francisco)
https://www.workatastartup.com/companies/wasmer
syrusakbary
·4 bulan yang lalu·discuss
Well, with the help of AI now you can have Fast, Affordable, and Correct.
syrusakbary
·4 bulan yang lalu·discuss
Just set it to MIT :)
syrusakbary
·4 bulan yang lalu·discuss
Thanks Yuri. Keep up the good work
syrusakbary
·4 bulan yang lalu·discuss
Actually agree with you here. It will be a good idea to add docs for the CLI and the WebAssembly sandboxing
syrusakbary
·4 bulan yang lalu·discuss
Yet... stay tuned!
syrusakbary
·4 bulan yang lalu·discuss
Thanks Ben! Took us a bit to figure out the best architecture for it, but once it became clear then it was just a matter of implementing the missing bits.

I think the fact that WASIX is much more mature now have helped to increase development speeds quite a bit!
syrusakbary
·4 bulan yang lalu·discuss
Yes it can :)
syrusakbary
·4 bulan yang lalu·discuss
Yes, this should be fully possible.

We actually believe Edge.js will a great use case for LLM-generated code.
syrusakbary
·4 bulan yang lalu·discuss
> 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 `edge` in your terminal and have things running, so that's why we point to the Node.js docs.

> But why the need of --safe then? What's the difference between using it and not using it?

Edge.js currently runs without a sandbox by default. The main reason for this is two fold: native currently performs a bit better than with the Wasm sandbox (about 10-20% better), and because we wanted to polish more the Wasm integration before offering it as default.

> $ edge pnpm run dev > What is this doing?

This is making the `node` alias available for anything that you put after edge. This allows pnpm to use the edge `node` alias instead of your platform node.

Things will be installed as usual, in your `node_modules` directory