jj VS rkyv

Jujutsu is along the lines of what you describe: https://github.com/martinvonz/jj

You can drop it in and work seamlessly from git repos

Pull Requests (or Merge Requests) are merged only when (1) all of the automated tests pass; and (2) enough necessary reviewers have indicated approval.

Git doesn't tell you when it's necessary to have full test coverage and manual infosec review in development cycles that produce releases, and neither do Pull Requests.

https://westurner.github.io/hnlog/#comment-19552164 ctrl-f hubflow

It looks like datasift's gitflow/hubflow docs are 404'ing, but the original nvie blog post [1] has the Git branching workflow diagrams; which the wpsharks/hubflow fork [3] of datasift/gitflow fork [2] of gitflow [1]has a copy of in the README:

[1] https://github.com/nvie/gitflow

[2] https://github.com/datasift/gitflow

[3] https://github.com/wpsharks/hubflow?tab=readme-ov-file

https://learngitbranching.js.org/ is still a great resource, and it could work on mobile devices.

The math of VCS deltas and mutable and immutable content-addressed DAG nodes identified by 2^n bits describing repo/$((2*inf)) bits ;

>> "ugit – Learn Git Internals by Building Git in Python" https://www.leshenko.net/p/ugit/

SLSA.dev is a social construct atop e.g. git, which is really a low-level purpose-built tool and Perl and now Python porcelain.

jj (jujutsu) is a git-compatible VCS CLI: https://github.com/martinvonz/jj

"Ask HN: Best Git workflow for small teams" (2016)

You will probably like Jujutsu, which takes much inspiration from Mercurial: https://github.com/martinvonz/jj

It isn't a 1-to-1 clone, either. But tools like revsets are there, cset evolution is "built in" to the design, etc. There is no concept of phases, we might think about adding that, but there is a concept of immutable commits (so you don't overwrite public ones.)

It also has many novel features that make it stand out. We care a lot about performance and usability. Give it a shot. I think you might be pleasantly surprised.

Disclosure: I am a developer of Jujutsu. I do it in my spare time.

I have created a discussion. Thank you both

https://github.com/martinvonz/jj/discussions/2691

> why don't version control systems (especially ones that can change history) have undo/redo functionality out of the box?

It's true. And Jujutsu has undo functionality out of the box, too. It's not just Sapling. :) https://github.com/martinvonz/jj

Git made the only choice a popular VCS can make. History rewrites will exist, period. If you're opposed to history rewrites, then git gives you the tools to ensure the repos you control are not rewritten, and that's all it can do in a world where people have control of their own computers.

If Fossil ever becomes as popular as git, people will create software that allows history rewriting in Fossil, and that's fine. People will do what they want on their own computer, and I think it's morally wrong to try and stop that.

Another user in this thread linked to jj [0], an alternative git client that does some pretty weird things. For example, it replaces the working tree with a working commit and commits quite often. I like git and that seems weird to me, but I'm not offended, people can do what they want on their own computer and I have the tools to ensure repos under my control are not effected. That's all I can hope for.

[0]: https://github.com/martinvonz/jj

I recently found out about another project called jj: https://github.com/martinvonz/jj. It takes inspiration from Pijul and others but is git-compatible.

https://github.com/martinvonz/jj

I think maybe both fossil and bitkeeper are more intuitive too.

Did you try any of those?

And before you ask: This only provides partial zero-copy support in strings and byte arrays like serde. But it's not like rkyv which constructs validated references into the data.

Regarding JSON, what kind of other implementation do you have in mind? I've seen e.g. `rkyv` which looks really neat (https://github.com/rkyv/rkyv/issues/85). So far `serde_json` is providing a clean surface API but maybe there's best solution?

Thank you for your concern. I've done plenty of projects that go beyond a "Hello World" such as a GPU accelerated password cracker. I am starting soon a C++/Rust job. I already contributed to codebases I didn't write.

rkyv is awesome because it supports full zero-copy deserialization. You can serialize your HashMap to a file. Later you can directly use the HashMap from the file without creating and populating a new HashMap in memory (rkyv directly indexes into the raw bytes). For even faster access times you can even mmap the file.

I had the same problem when trying to deserialize a big struct with rkyv: see rkyv#277.

Any chance of working with zero-copy deserialization frameworks? like https://github.com/rkyv/rkyv or capnproto

Hi, you seem to know a bit about Sanakirja!

It stores 4kb blobs, right? Does Pijul first parses the data (copying it to other allocations), or uses the data as is? I mean, there are some libraries like cap'n'proto[0] and rkyv[1] that can directly use the file contents as an in-memory data structure, I was wondering if Pijul did anything like that.

I mean, is this btree page [2] stored exactly like this on disk, and does Pijul exploits that to avoid further copying data?

(I guess there's a trouble with compression there: to decompress you really need to write in another buffer)

Also, is the I/O done with something that prevent userspace copies like mmap or io_uring, or does it eventually calls read() to copy the data to its own buffer?

I want to build something like Sanakirja, but with those features, so I'm wondering if there's any overlap.

[0] https://github.com/capnproto/capnproto-rust

[1] https://github.com/rkyv/rkyv

[2] https://docs.rs/sanakirja-core/latest/sanakirja_core/btree/p...

I think https://github.com/rkyv/rkyv does this. Also capnproto like was mentioned here, and perhaps https://docs.rs/zerocopy/0.6.1/zerocopy/index.html too

It's been two months since the last major rkyv release, and three months since the last major feature release. After all that time, I'm proud to announce that rkyv 0.7 is finally out!

After roughly two months of work, rkyv 0.5 is finally out!