DataFixerUpper VS awesome-wasm-langs

You don't need to load a world in every version and in fact this is not recommended because later versions fix various bugs with converting older worlds and with the exception of Beta 1.3 (Alpha to Region*) and release 1.2 (Region to Anvil*) only chunks you've loaded will be converted (since 1.13 there is an "optimize world" feature which can force a full conversion and is recommended mainly to avoid lag due to the game converting chunks on the fly; modern versions change data formats so often Mojang created an entire "data fixer" library and data versioning so it can tell exactly what version a file was last saved in and update it properly, anything without a version tag is assumed to be pre-1.9, which barely changed aside from Alpha-Region-Anvil).

No need to guess, we know pretty much exactly what this is referring to, because it was performance changes in one of the open-source components, DataFixerUpper. The code is open to the public, and you can look at the changes yourself if you want to. It's somewhat technical but I'll try to explain.

Read it and weep! https://github.com/Mojang/DataFixerUpper

java and generics mentioned in the same headline and noone's linked the funny library yet, smh

And I work on Minecraft.

DataFixerUpper, particularly codecs

You can write a library for profunctor optics, something that is usually used in functional languages like Haskell, in Java, but that doesn't mean it's convenient or even practical to use.

Cross-language support for over 30 programming languages for eBPF user space programs

wot

Just about every language can compile or transpile to WASM:

https://github.com/appcypher/awesome-wasm-langs

There are also curated lists of languages that compile down to Wasm available on Github, so there is a ton of opportunity to choose your own adventure.

My current plans are to investigate TinyGo / C# NativeAOT-LLVM / other languages that can compile to Wasm once our host side stabilises a little bit (lots of churn right now!)

Yeah, it's pretty cool. Here's a nice list of all the repositories and stuff like that

It’s planned to use WASM, which would allow to use basically any language you’d want (ok, any lang having a WASM compiler or VM), including Lua.

While waiting for placement at Andela, I started something. I wanted to create a community of developers who had already worked on WebAssembly projects in the past. A bit of a back story is in order now. During my exploratory phase before I settled for web development, Web Assembly was announced. So on a whim, I created a Repo to keep track of languages that compile to web assembly. The repo ended up getting over three thousand stars. I honestly didn’t expect it to blow up as much as it did, but it did. That feat fueled my interest in Web Assembly. As I was saying, I wanted to gather Web Assembly developers together for a purpose - to create a common web assembly runtime, a canonical runtime. My attempt at community building didn’t go so well. I sent a couple of emails, and DMs to no avail, or so I thought. It was during this time that Syrus Akbary reached out to me, he pitched the idea he had to build an awesome web assembly runtime, Wasmer, and that he would want me to be involved. He was really excited, and so was I. The only thing was that he said he had to lay down some of the groundwork first. So he worked on it for about a month. Now that I think about it, I should have stuck to him while he laid down the work because when he showed me the progress he had made, I was awe-stricken, but also disadvantaged. A lot of work had been done. Here we were trying to build the web assembly runtime that would take the world by storm, but my knowledge of Rust was meager. Keeping up was hard. Eventually, I had to leave the project, he was incorporating Wasmer as a company, so relocation was being discussed but I wasn’t interested in going to the US. But I think the major deciding factor for me was that I didn’t really align with the management of the project.