Live data from Hacker News

Viewing profile — schacon

schacon

HN member
Joined
Wed, Mar 12, 2008, 7:26 PM UTC
HN karma
2,438
Public activity
288 items

About schacon

works at GitButler. loves kittens, ruby and git.

Recent public activity

  1. story
  2. story
  3. comment
    Comment #48621001

    In California, it's capped at a knowable amount when you buy the home and pegged at the sale price. You know what it is and what it always will be when the transaction happens. The…

  4. comment
    Comment #48620878

    Love it. In fact, we should have expanded it to be a "millionaire tax" where everyone who has a home worth more than $1M needs to pay a one time $50k+ tax to the highly efficient s…

  5. comment
    Comment #48490079

    Relicensing under any other license, including the LGPL, is exactly the same thing. Either the reimplementation copies protected expression, in which case it would be required to b…

  6. comment
    Comment #48490014

    > Would you be happy for someone to do the same with the GitButler source code? Honestly, that would be pretty awesome. We would be flattered.

  7. comment
    Comment #48473976

    Nice, I haven't dug into this yet. If we can get this usable, it would be pretty cool to have a small lib or a series of much smaller, directed libs that can be used by simpler int…

  8. comment
    Comment #48473886

    Not yet. I have a PR with a WASM experiment based on an earlier build, but it's not integrated. It's on my list of things to try. I _did_ get it working for some things, so it's cl…

  9. comment
    Comment #48473849

    Well, there's lots of really interesting opinions here from a lot of armchair lawyers. To clarify, my stance on this is that the reimplementation did not copy protected expressions…

  10. comment
    Comment #48472821

    GitButler's source code is available, so we're not asking you to trust us much at all. https://github.com/gitbutlerapp/gitbutler

  11. comment
    Comment #48472815

    A feature complete, reentrant, linkable library. Reading the article often helps with questions like this.

  12. comment
    Comment #48472797

    As mentioned, we also work on the Gitoxide project and Byron is a member of our team. We are well aware of all large community efforts and we're also cohosting the Git Merge confer…

  13. comment
    Comment #48472633

    I think Byron (Gix author/maintainer) is one of the most excited people about the Grit project. Gitoxide is great and we will continue to push it forward. Grit is an orthogonal pro…

  14. comment
    Comment #48472293

    I see it differently. I look at it as if I had written this code myself, using this same approach. Look at the docs, look at the tests, look at the source, implement something that…

  15. comment
    Comment #48470918

    To be clear, I 100% did not make libgit. I did help the libgit2 project get off the ground.

  16. comment
    Comment #48470896

    I'm assuming you didn't read the article, since I'm pretty sure I covered all of this, but I'm happy to respond. Don't bother. It's probably not for you. It's slower, more obtuse, …

  17. comment
    Comment #48470838

    We're choosing a license that is usable by the entire community. Our goal is a linkable library, which makes GPL impossible. If we had chosen to go with LGPL or GPL with linking ex…

  18. comment
    Comment #48470797

    Gitoxide is also developed primarily by Byron, who also is part of the GitButler team. We're pushing both projects forward.

  19. comment
    Comment #48470790

    I'm happy to take contributions if you want to throw some tokens at it. Bug reports would be amazing, since I haven't tested it for real very much (enough to know you can do basics…

  20. comment
    Comment #48470760

    I started the project as Gust, but felt like Grit was such a better name. I asked Tom if I could boot the name back up again because I always liked it and he said it was fine. Also…

  21. comment
    Comment #48470735

    I would not use this except to help us test it if interested. I'm announcing it because it's interesting and a milestone in the breadth of test coverage it can pass. It almost cert…

  22. comment
    Comment #48470705

    libgit.a isn't reentrant. It will call `die()` on many errors. If you link to it in a long running binary, it will kill your process on error. Libgit2 is meant to address this and …

  23. comment
    Comment #48470689

    My intent with this project is not to replace Git in any way. I don't care about the CLI part of this project. The point is to provide a feature-complete reentrant linkable library…

  24. comment
    Comment #48470661

    I would also be interested. I haven't dug into this at all yet, nor have I tried to optimize the size (or really, anything else). However, the library part will be less than half o…

  25. comment
    Comment #48470625

    It's not for Rust, it's for Library. Well, it's sort of for Rust. GitButler is written in Rust and Jujutsu is written in Rust and we're both depending on fork/exec'ing to an unknow…