steveklabnik

7 ms·

1.
by steveklabnik 5d ago
Certainly meant to be more of a teaser. We’ll get there. It’s very possible some of your proposals are similar, I’m not familiar with them specifically so I can’t say. But there’s just a lot of stuff that’s already working in existing syste
2.
by steveklabnik 5d ago
We are huge believers in stacked diffs, both for humans and machines. That said, everyone is trying to figure out what code review means in this new world, so we're open to things changing here. You can get claude to produce small, foc
3.
by steveklabnik 5d ago
It's certainly not the case that no open source projects use monorepos, you are right that the BSDs do as well. It's that those repositories are still orders of magnitude smaller than the ones that are inside of companies. Monorep
4.
by steveklabnik 5d ago
I found this reply very confusing... is this an atproto joke?
5.
by steveklabnik 5d ago
Trying to keep it high level here. Explaining this is important, but it's just an entirely different kind of post. That post would be deep in the weeds, and this one is at a high level. Both matter, for sure. And we'll put out mor
6.
by steveklabnik 5d ago
Thanks Rick! I realize this post is light on technical details. I expected this kind of reaction from HN, which is also fine. The goal here is more to share anything about what it is that we've been doing; a lot of people assumed tha
7.
by steveklabnik 6d ago
Sort of! It's not that we're against general purpose protocols, it's just that they need to be fit for purpose. For folks for whom the git protocol works for them, we're happy to support it. We just need more than that.
8.
What Comes After Git(ersc.io)
17 points by steveklabnik 6d ago|4 comments
9.
by steveklabnik 7d ago
For whatever it's worth, I read zero negativity about Rust in the title or content.
10.
by steveklabnik 8d ago
I don't know enough about the details to speak to it.
11.
by steveklabnik 8d ago
You can use a "subtype predicate" for this: https://learn.adacore.com/courses/Ada_For_The_CPP_Java_Devel...
12.
by steveklabnik 8d ago
This is called "pattern types" in Rust land, as your parent mentioned, and is exactly the kind of work being talked about. NonZero isn't a hack: it's an example of a common pattern. If pattern types were available today,
13.
by steveklabnik 8d ago
> As you can see, it has many convenience methods to make it easy to work with, compensating for the loss of the Rust enum. Also, Rust does try to do some of these optimizations itself. These aren't exposed in the stable language to
14.
by steveklabnik 9d ago
Pretty much all of Nathan's work is. The Curse is so intense, and it only gets more so from there.
15.
by steveklabnik 11d ago
> if they want that information from the borrow checker how would they get it? If you want to compare if two pointers point to the same place, you use https://doc.rust-lang.org/stable/std/ptr/fn.eq.html Ru
16.
by steveklabnik 11d ago
> the other extreme These aren't the only two options. This > Pip installs everything system wide does not inherently mean > you can't have different versions of the same package
17.
by steveklabnik 12d ago
Because it became a meme virtually everyone who says this are actually joking and not serious. They'll move on to whatever the next meme is.
18.
by steveklabnik 13d ago
Sort of but also no. Intrusive lists are not likely to ever be possible in safe code, almost by definition.
19.
by steveklabnik 13d 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
20.
by steveklabnik 13d 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
21.
by steveklabnik 13d ago
Not directly relevant.
22.
by steveklabnik 13d 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
23.
by steveklabnik 13d 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
24.
by steveklabnik 13d 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
25.
by steveklabnik 14d 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
26.
by steveklabnik 14d 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&
27.
by steveklabnik 14d 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
28.
by steveklabnik 14d 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
29.
by steveklabnik 14d ago
No clue, I’ve never heard of that. What does it tell you?
30.
by steveklabnik 14d 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

More ›