Review Wasm runtime table

[andreaTP]

Hi @pretzelhammer !
Thanks for the openness and for sharing your blog posts in GH!

I got a link to your last blog on the Extism Discord and, although I think the article is well written and highly useful there is a section (I care about 😅 ) that I believe can be improved.
In this table, you are reporting the GH Stars of the project:

rust-blog/posts/rust-in-non-rust-servers.md

Lines 253 to 262 in b7c37ef

	| Language | Wasm runtime | Github stars |
	|-|-|-|
	| JavaScript| built-in | - |
	| Java | [GraalWasm](https://github.com/oracle/graal/tree/master/wasm) | 20.3k+ |
	| Multiple | [wasm3](https://github.com/wasm3/wasm3) | 7.3k+ |
	| Go | [Wazero](https://github.com/tetratelabs/wazero) | 4.9k+ |
	| Multiple | [extism](https://github.com/extism/extism) | 4.2k+ |
	| Python | [wasmer-python](https://github.com/wasmerio/wasmer-python) | 2k+ |
	| PHP | [wasmer-php](https://github.com/wasmerio/wasmer-php) | 1k+ |
	| Ruby | [wasmer-ruby](https://github.com/wasmerio/wasmer-ruby) | 500+ |

"Comparing" those different projects in the same table and using GH Stars as the ranking mechanism is misleading in my opinion, some top concerns:

• the GraalWasm stars are referring to the entire Graal project
• Extism is not "per-se" a Wasm runtime, but wraps other runtimes
• Wasm3 is a C interpreter (at best of my understanding), it can be used in other runtimes because it can be compiled to wasm itself

I'm happy to help steering this section if you are open to it (would you be open to review a PR?), or the suggestion is to have an unranked list of relevant projects (with the current content).

Bonus:
I'm a maintainer of a Wasm runtime, Chicory, I'll be happy to add the project name if you think it's appropriate 🙏

[pretzelhammer]

I didn't put a ton of thought or effort into that table, so if you think you can improve it then go for it, I'm open to reviewing your PR.

I will say that I do like github stars as a sorting mechanism because number of github stars serves as a good quantitive proxy metric for quickly gauging a project's maturity, documentation, stability, popularity, etc. It's not always accurate, but I feel like it's better than nothing. I'm not thrilled at the idea of removing it, because I do think having it provides some value for readers. Ideally it would be replaced by another better quantitive proxy metric, like all-time downloads of the project via the project's language's main package registry (e.g. npm for js, maven for java, crates.io for rust, etc).

Anyway, feel free to make a PR and we can continue the discussion there and hopefully reach a result we're both happy with.

[andreaTP]

Thanks for getting back! I'll give it a spin tomorrow and submit a PR 👍