DataFixerUpper VS Immer

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.

```

It looks like it’s mutating, but both the reducers and update() uses immer* under the hood, so we still respect immutability under the hood.

Cami supports redux devtools so you can use that for time-travel debugging too!

—-

* https://github.com/immerjs/immer

I heard that immutability libraries like immer.js [0] help with this. Anyone go this way and had good success? Is this 'the way'?

[0]: https://immerjs.github.io/immer/

So, that's what we built, and we built it in the most obvious way — using JavaScript Proxy objects to track mutations and reflect those changes across Appsmith’s framework. Initially things looked good — it worked, aside from a few hacks to make some data types work with map and set, and we were following the example of other projects that had similar requirements. If it was good enough for them, it should be good enough for us, right?

But is immer really the ultimate answer? The performance problem of immer is more prominent in large arrays and deep-level object scenarios. See this issue description, many authors in the community began to try to make breakthroughs, and noticed that structura and mutative, I found that it is indeed many times faster than immer as they said, but it still fails to solve the problem of both fast speed and good development experience. I will analyze the two issues in detail below.

I like immer for this kind of thing: https://github.com/immerjs/immer

It gives you immutable updates without getting bogged down in FP abstractions.

I've always been a huge fan of immer for these case. For your code, it would simply turn into setGridData((prev) => produce(prev, draft => applyChanges(changes, draft)) but I recommend you go over their documentation to fully understand how it works

If you're trying to make things actually immutable, Object.freeze and deep copies can clutter things up pretty good, have you considered using something like immer? (https://immerjs.github.io/immer/)

If you want to set up from Context, Zustand is your best bet. It offers an extremely simple API that lets you create a store with values and functions. Then, you can access that store from anywhere in your application to read and write values. Reactivity included! If you want to store nested object data in your store, consider using Immer alongside Zustand to easily change nested state.