steveklabnik

5 ms·

31.
by steveklabnik 1mo ago
What I mean is, you manage the index with the same commands that you manage commits with. The emphasis is on "with separate tools" not "manage the index". I am super curious as to what you mean specifically, but I also k
32.
by steveklabnik 1mo ago
It is absolutely possible, but all of the data we currently have shows that reducing the amount of code that could possibly have the error has meaningful effects on the number of vulnerabilities. Mitigation may not be the same as eliminatio
33.
by steveklabnik 1mo ago
Not directly relevant.
34.
by steveklabnik 1mo ago
We are also sort of at a "bespoke factory" stage where building a factory means doing it around your specific codebase, each of which has their own needs and quirks. Just taking one of these wholesale from one company and using it
35.
by steveklabnik 1mo ago
writing prose and writing code are two different things I can get good code out of LLMs. I can rarely get good writing out of them. Maybe it's a skill issue, but it's not inherently a contradiction that they're better at some
36.
by steveklabnik 1mo ago
I love the index, and often have "uncommitted" stuff lying around. jj makes doing this easier because you represent the index as an unnamed commit, and everything just works, as opposed to needing to manage the index vs committe
37.
by steveklabnik 1mo ago
We plan on building everything as individual building blocks, that you can use or not use as you wish. Initially we won't be offering our own CI directly, you'll bring your own. We use Buildkite internally, so we'll probably
38.
by steveklabnik 1mo ago
You give Google the right to take your patch and use it under any license. There is no assignee because there is no reassignment. (Also, as I just said in another comment, I forgot about trademark: if the community did want to fork, they&
39.
by steveklabnik 1mo ago
Since I posted previously, I realized I had forgotten trademark entirely, and Google does own the trademark for jj. (See my other comments about the Mozilla/Rust connection, it was the same back then too). It's not an issue for in
40.
by steveklabnik 1mo ago
Because jj is backend agnostic, you can use it with whatever VCS you'd like. git is very common. So it has the exact same amount of "lockin" as git does. If there's interest in alternative implementations, then they&#x27
41.
by steveklabnik 1mo ago
No clue, I’ve never heard of that. What does it tell you?
42.
by steveklabnik 1mo ago
I don’t actually know who owns the org offhand. My point is not that it is “not Google owned” but to point out the specifics, which really matter. “Google owned” to me implies that they own the copyright to contributions, which they very mu
43.
by steveklabnik 1mo ago
Doesn’t really change it at all. Because there’s no copyright assignment, it’s not any different than any other open source project that doesn’t do it, there’s no ownership to actually move. It would just be about socially what is considere
44.
by steveklabnik 1mo ago
Various git commands can drop the metadata, so it’s not guaranteed to stick around.
45.
by steveklabnik 1mo ago
It gives Google the ability to use the source code under whatever terms they want. It does not change the Apache licensed code at all, which can still always be used under that license. There is no “the jj organization”.
46.
by steveklabnik 1mo ago
It’s a usage pattern, not a feature. It’s a really common way of working with jj: https://steveklabnik.github.io/jujutsu-tutorial/real-world-w...
47.
by steveklabnik 1mo ago
Legal ownership does not belong to a single company. All copyrights are still held by each individual contributor, and they're available to be used under the Apache 2 license. The CLA means Google also has a license to the code to do
48.
by steveklabnik 1mo ago
Oops you’re not wrong, there’s just a lot of comments and it’s hard to keep threads straight, my bad :)
49.
by steveklabnik 1mo ago
We’ll find out!
50.
by steveklabnik 1mo ago
Thanks man :)
51.
by steveklabnik 1mo ago
While this is true and I agree with you, to be clear we do way more than just a nice UX. There is a lot of deep technical work going on here. If anything the UX isn’t the selling point, we are an infrastructure company at heart.
52.
by steveklabnik 1mo ago
Yes. Stacked diffs are table stakes.
53.
by steveklabnik 1mo ago
Yes, he joined a few months ago, this is just getting it onto the site :)
54.
by steveklabnik 1mo ago
We tested it in mobile, but several people pointed out that we have more performance work to do to make sure that the animation is fast on lower-end hardware. I don't know what phone you're using, but we'll get it fixed regar
55.
by steveklabnik 1mo ago
While this is true, we do care about performance tremendously, and the animation not having good performance cuts against that, so I think it's a very fair criticism. Paying attention to details matters.
56.
by steveklabnik 1mo ago
Thanks! Yes, it's important to realize that git is multiple things: the on-disk repo format, the CLI, and the wire protocol. Each has their own challenges, just like any project, but they can be tackled independently. But at the end of
57.
by steveklabnik 1mo ago
I joined ERSC ten months ago! The things I am most interested in right now are jj and llms. And the intersection between the two. I'm thinking a lot these days about how agentic development is changing our industry, with source control
58.
by steveklabnik 1mo ago
I like to compare Google and jj to Mozilla and Rust: Google employed Martin and some other maintainers, but it's always been an OSS project under the Apache 2.0 license. That being said, there's a few things that lead to this perc
59.
by steveklabnik 1mo ago
Thanks, I'm a Windows user and use Chrome myself, and on my machine it works great, but it's a pretty beefy box. I mentioned this downthread to someone else, but I've filed a bug internally and we'll make sure that it&#x
60.
by steveklabnik 1mo ago
I left a lengthy comment below about how we'll be supporting git as well. I have been a member of this community for a very long time. Posting here is something I just do. jj is already pretty well known here, there's articles abo

More ›