voxelmetaverse VS pyodide

Minecraft may actually be closer to the metaverse than commonly believed:

Since the introduction of BungeeCord in 2012 (and then Waterfall and Paracord), it has become increasingly popular to link together multiple servers to act as a gateway to different virtual worlds on different servers. Most of the top popular "servers" are in actuality multiple servers joined together, somewhat decentralized, though still centrally managed.

Even before Bungee, the reign of Bukkit (2010-2014) introduced a plugin API system allowing for managing multiple worlds. To this day the "Multiverse" plugin remains among the top plugins. The multiverse, not the metaverse, but a related concept.

It wouldn't be too far of a leap to link together unrelated Minecraft servers.

Regarding "you can certainly not expand the protocol -southerntofu" - the Minecraft protocol is commonly expanded by modders. In fact, it is specifically designed to be expanded, since the introduction of Plugin Channels in Minecraft 1.1: https://wiki.vg/Plugin_channels. Forge modders frequently enhance the protocol to support new functionality far beyond what was possible in the original game.

"new media forms and new mediums of access (web, mobile, PCs, AR, etc.)" vs "you can only run Minecraft where Microsoft distributes it (unless you crack/RE it)" - granted, but there are multiple unofficial efforts to develop new ways to access Minecraft servers, including through the web. My humble attempt at building such a client: https://github.com/voxel/voxelmetaverse

Not coincidentally, I called it "Voxel Metaverse", thinking along the same lines as you were, and had high aspirations. It did not pan out, though we had some cool features including connecting to Minecraft servers, embedding web page content in a 3D space (including interactivity with voxel-webview, still working in the demo: https://voxel.github.io/voxelmetaverse/) and I wrote a retrospective about its successes and failures earlier this year: https://medium.com/@deathcap1/6-years-after-6-months-of-voxe... but it showed a lot of promise in what could be done to build a decentralized distributed malleable virtual world. Voxels are particularly attractive in my opinion due to the ease of content creation.

Other more recent efforts to build web-based Minecraft clients include https://github.com/PrismarineJS/prismarine-web-client and https://www.spigotmc.org/resources/websandboxmc.39415/, both are currently quite limited, but its only a matter of time/effort to complete the implementation and not a fundamental technology limitation. There are dozens of unofficial Minecraft-compatible clients, in various degrees of completeness: https://wiki.vg/Client_List

Vivecraft started in 2013 to allow a VR experience in Minecraft, and there is now an official Minecraft VR port though Vivecraft still has its fans. There's official mobile and console clients (Bedrock Edition), and although not officially interoperable with PC servers, there are also 3rd party solutions to bridge the two, including Dragonet DragonProxy and GeyserMC.

Will Minecraft blaze the way forward into what becomes The Metaverse? Honestly, maybe not. Mojang may not see the same potential in Minecraft as I do, but I feel the modding community is onto something developing projects on the edges of a hypothetical Minecraft Metaverse. If it isn't Minecraft itself, I am convinced a similar game will play a fundamental role in the development of what we come to know as the metaverse.

Voxelmetaverse, a voxel game platform based on voxel.js

Live demo: http://voxel.github.io/voxelmetaverse/

Source code: https://github.com/voxel/voxelmetaverse

I had big ideas for it but didn't get too far, after several years of working on it. Just published a retrospective today: https://medium.com/@deathcap1/6-years-after-6-months-of-voxe... - it could be developed much, much further.

We implemented an in-browser Python editor/interpreter built on Pyodide over at Comet (our users are data scientists who need to build custom visualizations quite often, and the most familiar language for most of them is Python).

One of the issues you'll run into is that Pyodide only works by default with packages that have pure Python wheels available. The team has developed support for some libraries with C dependencies (like scikit-learn, I believe), but frameworks like PyTorch are particularly thorny (see this issue: https://github.com/pyodide/pyodide/issues/1625 )

We ended up rolling out a new version of our Python visualizations that runs off-browser, in order to support enough libraries/get the performance we need: https://www.comet.com/docs/v2/guides/comet-ui/experiment-man...

Thank you! Yes, one of the items in the Roadmap is support for Pyodide (https://github.com/pyodide/pyodide) for running in-browser python on the results of each of the code blocks! This should allow most ML libs to be usable in-browser! This is pretty high-up on our priority list.

If I understand correctly, WASM only makes sense for compiled languages, you can run the python interpreter in WASM of course[1], but that will be at a significant performance disadvantage to the native javascript interpreter, and it's also something that has to be loaded every time you load the website.

[1]: https://github.com/pyodide/pyodide

If you absolutely need something comparable to Sympy, then one option might be to figure out how to best call Sympy from Rust. e.g. - RustPython, although it seems like Sympy isn't supported yet - Pyodide, and figuring out how to run it outside of a web browser. Probably also not very easy. - PyPy, and having a pretty simple Python binary for every platform - ...

For running programming languages other than JavaScript in the browser there is Emscripten and WebAssembly. There is v86, where a Linux build is compiled to WASM. Folks have written QuickJS into a Linux build compiled to WASM, Node.js into the Linux buildroot https://github.com/cemalgnlts/now, so Python or CPython can be written to the image and loaded into the browser as WASM as well https://github.com/pyodide/pyodide.

There's a Python runtime that runs on WebAssembly (https://github.com/pyodide/pyodide). I have no idea what it's like, I've never used it.

Still in a quest to provide some tooling to quickly compose documentation websites: https://github.com/synw/docdundee . As I have tons of libs to document and was tired of managing restructured language for readthedocs I started with this, and now it has executable Python examples in the frontend via a Pyodide wrapper composable: usePython

This project's brand new and a lil hacky, but I've already reached out to the scikit-learn team, and they recommended that I experiment with using Pyodide as an alternative backend for the Python bridge.