Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

The trick is to not copy the data, but to pass pages around.


sort by: page size:

Or better: The data URI gets copied.

You could treat them as files and use the file copy-paste mechanism.

But that makes a copy first, and only later notices that the pages are the same and merges them again.

Better to not make copies in the first place.


True, but flipping through the book to copy all pages is too much effort to copy the file to my remarkable instead.

You have to copy less than you think. Because the data is immutable, you can share everything but the changed fields.

In one case, the fastest way would be to not have to copy it, just reuse the same file.

Just copy them using File -> Copy

Transferables are fast, but they are still a copy operation.

I'm pretty sure it's the reference that makes the data not be copied.

You can still use File: Copy for a second, unrelated copy.

With OTP20, copying data isn't always necessary anymore :)

Is there a way to do this without involving the overhead of a full copy, though?

read, not copy. They upload the files up to their servers.

Nah, it’s just easy to copy if you lay it out. It’s software.

Do you really need to do a full copy? What if you had a shared page and notified the user process when the data in the page was available at a certain offset.

Take a look at this paper (FlexSC: Flexible System Call Scheduling with Exception-Less System Calls):

https://www.usenix.org/legacy/event/osdi10/tech/full_papers/...


The problem with that: retain meta-info when copying from machine to machine. Otherwise: yes.

These days I just use a network file browser to copy files. Easier that way.

Or on Windows, Xcopy.

There's already a copy function that does this.
next

Legal | privacy