Live data from Hacker News

Git implemented in Rust

github.com

31–40 of 122 posts

Re: Git implemented in Rust

#31
post #20

Earlier quoted context omitted.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

"Use" is allowed, redistribution of the original or derivative works is essentially what is not permitted.

I guess it depends on what you call «use». You can read the code, for sure, probably even save it on your disk (it may depend on your jurisdiction though).

But, can you compile it ? I'm not sure… Better ask your lawyer. And what about running the compiled binary ? I don't think you're allowed to do that.

Re: Git implemented in Rust

#32
post #3

I love to see people reimplementing existing tools on their own, because I find that to be a great way to learn more about those tools. I started on a Git implementation in Rust as well, though I haven't worked on it in a while: https://github.com/avik-das/gitters

Are you basing it off anything in particular? Like outside of just going through gits own source code?

Re: Git implemented in Rust

#33

Let's port already portable software to non-portable languages! Yay!

Rust is pretty darn portable as it is though. It runs on the major platforms. Are you thinking its Assembly or something? Everywhere FireFox is compiled to Rust has to run on, which is a lot of platforms.

Maybe it wont run on your toaster but if you are making git commits through your toaster you got other issues.

Re: Git implemented in Rust

#34
post #7

I like the changelog. Looks like a zero-effort way to publish something other people could make use of.

To be honest, I wish there was a movement for something like "literate changelog", where the CL was propely linked with something like a blog post, and specific repo versions. I guess Pull Requests sort of take that role.. But sometimes PR diffs aren't the same as annotated code in a blog post.

Re: Git implemented in Rust

#35

Let's port already portable software to non-portable languages! Yay!

If you really needed to run Rust code on some platform LLVM doesn’t natively support, it does allow you to compile to C. Presumably you could then compile that using whatever C compiler works for your platform.

Although Rust is not as portable as C, going through these hoops would mean that —- modulo codegen bugs —- the generated C code should still be as memory-safe as the original Rust code.

Re: Git implemented in Rust

#37
post #8

Earlier quoted context omitted.

Here is an implementation of a Ruby based kv store build on top of rugged, which is built on top of libgit2: https://github.com/ioquatix/relaxo-model It's so much fun, but not that practical for scalable websites.

>It's so much fun, but not that practical for scalable websites. Git based kv has a bit different purpose than the regular kv storage. They are intended for communication between entities, running in parallel, sort of transactional memory. They are not intended for users' data storage.

That sounds more like a tuple space than a KV store?

Re: Git implemented in Rust

#38
post #19

Earlier quoted context omitted.

That sounds nice and all but it's wrong in two major ways. First: GitHub has a Terms of Service which was somewhat-recently amended to make this license grant explicit: https://help.github.com/en/articles/github-terms-of-service#... "Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be view…

Pretty much all the TOS says is there's an implicit reproduction license (other users can see & fork the work) and possibly broadcast (the fork itself has the visibility of the original). Not adaptation, not use, not exploitation, … And that license grant is solely through github as a service, it's unclear that a local clone is even permitted.

That's... somewhat true. My main objection is to "the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use)".

The ToS doesn't say there's an implicit reproduction license, though; it says there's an explicit reproduction license.

The other licenses can still be argued to be implicit. For instance, you have a decent argument that local clones are an implicit license – GitHub provides a "Clone or download" button directly on the repo page, and it's one of the main use cases of GitHub. (Other arguments exist.)

Re: Git implemented in Rust

#40
post #3

I love to see people reimplementing existing tools on their own, because I find that to be a great way to learn more about those tools. I started on a Git implementation in Rust as well, though I haven't worked on it in a while: https://github.com/avik-das/gitters

Are you basing it off anything in particular? Like outside of just going through gits own source code?

Just reading source code is a whole different experience than actually implementing something yourself. Implementing something pretty much forces you to "be right" in your understanding, while reading can be anything from "really studying" to skimming.
Post reply on HN