preevy VS Immer

Feel free to star the Preevy repo here.

We at Livecycle, a Docker-centric company, are super excited to share some highlights from the event and discuss how we are developing our products, Livecycle Docker Extension and Preevy, to improve collaboration, feedback, etc., in the vision that Docker is moving with their recent development and announcement at DockerCon.

To learn more about how to use Preevy, just check out the docs site.

Historically, many developers have preferred to facilitate this type of collaboration with ephemeral preview environments that are triggered with every PR or commit. And indeed, we have built robust solutions like “Preevy” to facilitate the creation of these environments for dockerized applications on any cloud or Kubernetes cluster.

Preevy also integrates into your CI pipeline to convert your pull requests into easily shareable ephemeral environments

My typical day is filled with a couple of meetings, building the Lifecycle community on Slack, collaborating with projects and people, and creating strategies and content (videos, blogs, short forms for Twitter and LinkedIn) around the product to increase adoption. I heavily focus on the company’s Open Source offering called Preevy which helps create a preview environment using Docker Compose underneath.

Also, at Livecycle, we are building Preevy, which helps you create a preview environment for Docker Compose applications. Do check out https://github.com/livecycle/preevy. It's open source, and don't forget to leave a star to show your support.

Check out the docs here

A dedicated docs site with relevant technical information and how-to guides for people who want to use it

About “Preevy” - an open source tool that simplifies the creation of preview environments

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