3 ms·

So I had a look at the repo/branches at https://github.com/wasmerio/py2wasm https://github.com/wasmerio/py2wasm. This might be a nit, but in the spirit of OSS:

So I had a look at the repo/branches at https://github.com/wasmerio/py2wasm https://github.com/wasmerio/py2wasm. This might be a nit, but in the spirit of OSS: if I'd done this work, I'd have contributed it to upstream Nuitka. I definitely would not have forked a whole new GitHub repo and given it a completely different name. What's the rationale for creating a new project and calling it py2wasm? Am I missing something?

Ennea 3y ago
My first thought upon reading Nuitka's name in the article was along the lines of "I hope they've contributed some of this to Nuitka". Not a very nice trend.
- __s 3y ago
  What trend? Forking happens all the time. It's one of the benefits of open source. I've often made PRs on github to projects while shifting projects I work on to my fork since upstreaming can take months or often never happen Granted, Nuitka is an active project, but wasmer.io is going to have a much more focused desire with their changes that they can deploy, meanwhile getting it upstream will have to go through rounds of review & adjustments https://github.com/rustwasm/wasm-pack/pull/937 https://github.com/rustwasm/wasm-pack/pull/937 this small change took over 2 years to merge. Open source takes time
spencerflem 3y ago
Reading the blog post- they are contributing it upstream
- boomskats 3y ago
  Well, reading the blog post, they're announcing a whole new compiler. I'd encourage you to have a look at the PR their post links to.
syrusakbary 3y ago
Thanks for the feedback! I'm Syrus, main author of the work on py2wasm. We already opened a PR into Nuitka to bring the relevant changes upstream: https://github.com/Nuitka/Nuitka/pull/2814 https://github.com/Nuitka/Nuitka/pull/2814 We envision py2wasm being a thin layer on top of Nuitka, as also commented in the article (not a fork as it is right now, although forking got us into the proof of concept a bit faster!). From what we gathered, we believe that there's usefulness on having py2wasm as a separate package, as py2wasm would also need to ship the precompiled Python distribution (3.11) for WASI (which will not be needed for the other Nuitka use cases), apart of also shipping other tools that are not directly relevant for Nuitka
- theanonymousone 3y ago
  On a different note, will there some technical documents on how exactly to use it, e.g. exporting functions etc...? By the way is it an alpha release, usable for testing, or something in between?

Ennea 3y ago

My first thought upon reading Nuitka's name in the article was along the lines of "I hope they've contributed some of this to Nuitka". Not a very nice trend.

__s 3y ago
What trend? Forking happens all the time. It's one of the benefits of open source. I've often made PRs on github to projects while shifting projects I work on to my fork since upstreaming can take months or often never happen Granted, Nuitka is an active project, but wasmer.io is going to have a much more focused desire with their changes that they can deploy, meanwhile getting it upstream will have to go through rounds of review & adjustments https://github.com/rustwasm/wasm-pack/pull/937 https://github.com/rustwasm/wasm-pack/pull/937 this small change took over 2 years to merge. Open source takes time

spencerflem 3y ago

Reading the blog post- they are contributing it upstream

boomskats 3y ago
Well, reading the blog post, they're announcing a whole new compiler. I'd encourage you to have a look at the PR their post links to.

syrusakbary 3y ago

Thanks for the feedback! I'm Syrus, main author of the work on py2wasm. We already opened a PR into Nuitka to bring the relevant changes upstream: https://github.com/Nuitka/Nuitka/pull/2814 https://github.com/Nuitka/Nuitka/pull/2814 We envision py2wasm being a thin layer on top of Nuitka, as also commented in the article (not a fork as it is right now, although forking got us into the proof of concept a bit faster!). From what we gathered, we believe that there's usefulness on having py2wasm as a separate package, as py2wasm would also need to ship the precompiled Python distribution (3.11) for WASI (which will not be needed for the other Nuitka use cases), apart of also shipping other tools that are not directly relevant for Nuitka

theanonymousone 3y ago
On a different note, will there some technical documents on how exactly to use it, e.g. exporting functions etc...? By the way is it an alpha release, usable for testing, or something in between?