quokka VS Immer

For more features and details check out the official docs https://quokkajs.com/

Used to be true, but between Quokka.js for quick prototypes, Wallaby.js for running tests smartly within the IDE, and now Console Ninja which enables inline console.log within the VSCode while running servers for common tooling (webpack, vite). As well as continuously improving collaboration tools like Live Share, And it's become hard for me to find an argument that Webstorm is still better for productivity here.

I use https://quokkajs.com/ it has a free version!

There are some fantastic tools such as Quokka which make "more algorithmic" development very interactive and fun

There's also extensions like https://quokkajs.com/

Quokka.js

I’m a Clojure(script) dev learning TS. My Clojure REPL flow is Cursive + IntelliJ. The closest equivalent I’ve found is https://quokkajs.com for inline evaluation and https://wallabyjs.com for test evaluation. Both are paid products but have free 30 day evaluation periods. Both work in IntelliJ and VsCode.

If you want to code and practice your JS in a sandbox, I highly recommend using VS Code (if you're not already using that for your HTML/CSS) in conjunction with Quokka.js. If you use `console.log()` function to log your results, Quokka will output directly in the editor. There are online resources that do something similar like codesandbox.io but I've found it nice to have a local environment.

Immer is a lightweight package that simplifies working with immutable states. Immutable data structures ensure efficient data change detection, making it easier to track modifications. Additionally, they enable cost-effective cloning by sharing unchanged parts of a data tree in memory.

```

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/)