steveklabnik

5 ms·

1. 61.▲
   by steveklabnik 1mo ago

   Thanks! I don't have Opera installed on my Win11 machine, but I tried it in Edge and it's barely using anything, but I realize that I have something beefier than a shared GPU on it. I've filed a bug internally and we'll
2. 62.▲
   by steveklabnik 1mo ago

   We are not actively hiring at the moment, but will be in the future for sure.
3. 63.▲
   by steveklabnik 1mo ago

   There is active work in this area, yes! https://github.com/jj-vcs/jj/issues/3386 is the bug tracking the feature request, and there have been some recent PRs working on implementing this, see here for one exa
4. 64.▲
   by steveklabnik 1mo ago

   What is your browser/OS combo? Thank you for bringing it up, we can only fix things that we hear about, so I appreciate knowing that something is off.
5. 65.▲
   by steveklabnik 1mo ago

   What is your browser/OS combo? I am assuming it's the animation, we tested it thoroughly but there can always be bugs. Thank you for bringing it up!
6. 66.▲
   by steveklabnik 1mo ago

   It's in the post, but Martin will be continuing to work on jj itself as well as on our products, just as he did at Google, working on the open source jj but also their internal source control team. As a side note, jj has rules around c
7. 67.▲
   by steveklabnik 1mo ago

   As we initially roll out we will be doing that, yes. The reason is that our initial offering is enterprise shaped, and so won't have a self-service onboarding. Eventually we will not require the white gloves, but you have to start some
8. 68.▲
   by steveklabnik 1mo ago

   Not off topic! We should be respecting https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/A... . If we do not, that's a bug, and please let me know what browser/OS/whatever el
9. 69.▲
   by steveklabnik 1mo ago

   It's not so much that we will prevent individuals from using the product, we are just focusing feature development on the needs of companies and teams. Startups are hard, and you have to focus, and so that's where we are focusing
10. 70.▲
    by steveklabnik 1mo ago

    This sounds glib, but I mean it sincerely: we will make money by charging money to use the product. A free tier on source control hosting is just not economically tenable nowadays. I have built a career on open source, and so that bums me o
11. 71.▲
    by steveklabnik 1mo ago

    We have a colopholon! https://ersc.io/colophon Rust is the default language for all of our non-frontend web stuff, yes.
12. 72.▲
    by steveklabnik 1mo ago

    I wrote a bit about this here: https://news.ycombinator.com/item?id=49526190 I wrote about why I joined the company back when I did previously here: https://steveklabnik.com/writing/i-see-a-future-in-jj
13. 73.▲
    by steveklabnik 1mo ago

    We'll be saying more about this very soon, but the short version is this: we are not building a GitHub competitor in the way that SourceHut or Codeberg are. We are building infrastructure for enterprises, not a social coding site. Whil
14. 74.▲
    by steveklabnik 1mo ago

    Thanks! Martin left Google for this, yes.
15. 75.▲
    by steveklabnik 1mo ago

    Thank you! We liked our old look, but one funny thing about how things are going in the world: our old color scheme was too close to what happens when you ask Claude to generate a site, and so even though we paid a human to build it, we did
16. 76.▲
    by steveklabnik 1mo ago

    Fixing, thank you! (Martin joined back then, but we are posting about it today, so we should have the post date as today)
17. 77.▲
    by steveklabnik 1mo ago

    Working with Martin has been a real pleasure, and we'll have some more stuff to talk about very soon!
18. 78.▲
    The creator of Jujutsu has joined ERSC(ersc.io)

    265 points by steveklabnik 1mo ago|268 comments
19. 79.▲
    by steveklabnik 1mo ago

    To further this, "destructive move" as C++ calls it almost happened, but ended up not. So it almost had it the same way as Rust too.
20. 80.▲
    by steveklabnik 1mo ago

    You're welcome! Just to be extra clear about it, while there's clearly some dysfunction going on in WG21, I don't think Rust's process is free of it either. I do think there's a lot of pros to the way Rust does thin
21. 81.▲
    by steveklabnik 1mo ago

    I mean, what stops it is > this will likely require some additions to the contract specification. You need a lot more machinery to move this stuff to compile time, and not everything can be checked at compile time. The first example in t
22. 82.▲
    by steveklabnik 1mo ago

    C++ contracts are not a compile-time construct, they're a runtime construct. Take the example from the article. The contract trips at runtime, not at compile time.
23. 83.▲
    by steveklabnik 1mo ago

    Thanks for this! I vaguely knew most of it but it's great to hear more details. I think that my misunderstanding here is because I thought that the vote in Croydon back in March was the last chance to veto things, but re-reading https
24. 84.▲
    by steveklabnik 1mo ago

    One thing that I'm curious about regarding all of this: I thought all of this stuff landed in C++26, yet we are still getting papers like https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2026
25. 85.▲
    by steveklabnik 1mo ago

    It does not disable any checks at all. It adds some unchecked features. All checked features are checked all the time.
26. 86.▲
    by steveklabnik 1mo ago

    Yeah, just to be clear, I am not your parent, I just saw Rust mentioned and realized what was going on in this conversation, ha.
27. 87.▲
    by steveklabnik 1mo ago

    Any time. This stuff took me a while to wrap my head around, since I never worked at Google or Meta. I don't think I'm the best at explaining it yet either...
28. 88.▲
    by steveklabnik 1mo ago

    I’m not sure what a “commit with multiple commits” is. I direct we’re talking past each other slightly :) I think this is maybe what you’re asking about: with PRs, you often respond to feedback by adding new commits on to the PR. This is be
29. 89.▲
    by steveklabnik 2mo ago

    You are mistaken about what your parent is saying: they're saying that if you want a system untouched by LLMs, you must provide alternatives to those things, because those things have LLM-generated code in them.
30. 90.▲
    by steveklabnik 2mo ago

    The reason people like to work this way is that it lets you very effectively respond to review. You address them by amending the commit to incorporate the feedback. This enables good interdiff review, so you can re-review just the new stuff