Handle large files

[praneshr]

Try introducing the windowing technique to handle large DOM nodes.

[taeyangee]

Encounter the same problem，looking forward optimization~

[cczz598]

I need to diff large text(145k) with 90% difference, but actually the browser crashed when rendering large text.
I'm also looking forward your optimization~

[skyunBoss]

How long does it take

[praneshr]

@skyunBoss - I don't have a timeline for it. I'm experimenting with few techniques. But, I'll address this issue soon!

[Azrog]

Would the use of a web worker help?
https://developer.mozilla.org/fr/docs/Web/API/Web_Workers_API

[SamSamskies]

@praneshr I also have to support large diffs and my temporary solution is to display a spinner and put a message that this may take a while if the changeset is huge 😂.

Have you thought about using react-virtual (https://github.com/tannerlinsley/react-virtual) to solve the issue? Here's examples of using react-virtual https://codesandbox.io/s/github/tannerlinsley/react-virtual/tree/master/examples/sandbox.

[praneshr]

@SamSamskies Thanks for the comment. Yes, I've explored the windowing option. But, I don't have the bandwidth to work on it now. So, I cannot guarantee a release date. Sorry.

[SamSamskies]

@praneshr np. I'll try and take a crack at it if I get some bandwidth myself.

[SamSamskies]

Would the use of a web worker help?
https://developer.mozilla.org/fr/docs/Web/API/Web_Workers_API

I think the main problem is the number of DOM nodes generated for large diffs, so I don't think web workers would help much.

[souljuse]

I am guessing that the problem stems from the "diff" library in the dependencies. It has the same unsolved issue with large diffs -> kpdecker/jsdiff#163

I suggest using https://github.com/google/diff-match-patch for handling large diffs