Mitchell Hashimoto

@karrisaarinen Makes total sense, on both fronts.

You can sync (GitHub😅) issues to Linear. But yeah we are not super focused on the open source/public community. You have to be part of the workspace to see anything. Maybe with AI bots that actually becomes somewhat desirable. Our focus has been supporting companies that also have open source projects not necessarily OSS projects.

What is unclear to me is what people actually want some new GitHub to be. To me, the biggest challenge GitHub has always had is that it is trying to serve two very different worlds. On one side, it is a social network around code and open source. On the other, it is infrastructure for companies building software. Those two groups operate almost in opposite ways, so the product has always been some kind of compromise between them. Because those users are so far apart, it can fail both of them in different ways. Inside a company, you mostly just want to review and merge code. You are not discovering new code, and you are probably not forking things. You may have a monorepo, a known team, and a trusted environment. What you want from GitHub is efficiency and safety: PRs, review, ownership, CI, Actions, tests, security checks, and a clear path to getting code merged. Open source is different. It is much more public and much less trusted. You need better ways to figure out who is contributing, what to accept, how to manage the project, how to handle issues, and how to maintain trust with people you may not know. So are people asking for a new open source code hosting and social network, or do they want better private infrastructure for software teams? Or both? I would never choose to build both from the start. I think every product gets better when it is more purpose-built and designed around a specific need. You could maybe imagine some nested model, where private repos have a much simpler and more focused mode, but you can still exit that mode and browse around the public space.

Pretty standard situation for my configs... everytime I hit a typo typing a command I just alias that typo. I have `jj` aliased to `j` and `jjj` and `hh` and `ll` too. Total madness. But it works.

@karrisaarinen Not yet! I’ve heard good things! I think I will for sure for professional stuff but not sure if it’ll fit the open source needs I have too. (To your point of two personas!) I’d actually really love for linear to help the issue/PR part of OSS. Then we can fully separate forge.

@mitchellh have you tried Linear Diffs yet?

@procmarco @karrisaarinen The worst part is you don’t get a stable product either lol.

@mitchellh @karrisaarinen my hot take here is that graphite PRs are the worst, from a UI POV. They keep moving things around and changing shit, essentially a new experience every other month I'd like a stable product that just works thank you

@Dustin2023 @karrisaarinen We have a plan, I just didn't want to detract from my personal message around GitHub. The blog post discussion would've turned into discussing the merits of where we were going vs the motivation for leaving. We're close to the move, probably this week or next.

@mitchellh @karrisaarinen Understandable, but it doesn't seem like there's an actual viable replacement. I don't think I could have made the announcement without a plan of action. It feels like being hasty and I don't know that anything will change or anyone else will jump ship from it.

@mylifcc @karrisaarinen Hard to answer that without internal access. Matters how poison the well is.

@mitchellh @karrisaarinen With you on better-not-new. I'm in GH Issues + Actions daily, PR review UX is the rough one. The 'separate products, don't integrate' bit—parallel SKUs or true skunkworks?

It’s really not my obligation to help a trillion dollar company. They have the resources to help themselves. I’ve been posting about their shortcomings for over a year and even posted exactly what I’d do if I were in charge. I can’t effect any change without power. I’ve got work to do I left (in the process of leaving).

@mitchellh @karrisaarinen This is where I think you should have refrained from posting that you're leaving and instead focused on helping GitHub to improve to where it could be. I don't think the alternatives hold water to be its replacement.

@Sanity @karrisaarinen Mass market doesn’t care about this. It’s a cool idea but it’s not marketable directly like this.

@mitchellh @karrisaarinen What if repos weren’t hosted by a service at all? I’ve been prototyping freenet-git (very early): github.com/freenet/freene… — repos live on a p2p network, and PRs/issues/wiki are separate, interoperable components. No provider dependency.

@kdaigle In looking at this again I recognize every part of this architecture from obsessing over early GitHub blogs and talks but I don’t recognize “earthsmoke”

@mitchellh Smiled when I saw it 😂

@kdaigle RESQUE!! Haven’t heard that name in a long time.

@ibuildthecloud Yeah same. I used it for years of course before but I’m using it more than ever before and it’s because LLMs just fucking do it.

All those nix people I always make fun of, you'll be happy to know I'm using nix more these days. Come to find out it's pretty great once you don't have to know the nix language.

@fat Lil Fat

@fat Fat

At Pierre Computer Company we write all of our code for the machines. The machines:

@glcst @tursodatabase Every software eng double checks this at least once even after knowing the numbers.

I was planning to use UUIDs to represent the databases we have on the @tursodatabase Cloud. I got a bit worried that we would perhaps run out of UUIDs. I just double-checked and I think we'll be fine for the next year or so. Will use UUIDs for now, and if needed, rearchitect later.

@conradev libghostty doesn’t include a renderer! We only have our high performance render state that you can build any renderer on top. GPU, CPU, doesn’t matter!

@mitchellh what about embedded on something without a GPU? 😛

Turns out you can just replace Alacritty (embedded) with libghostty in your app and gain so much speed you can literally see it. Ghostty was built from day 1 with the goal of being embedded. And it’s showing!

@haveanicedavid @superdoteng Hope the fast one is libghostty? lol

@mitchellh wow, thank you for this. just experimented with shifting @superdoteng from alacritty to a GPUI-rendered libghostty core via your libghostty-rs bindings and, well…

Awesome to see! Let's replace the Alacritty core with libghostty-rs. If there are any shortcomings in the libghostty API I'll address them immediately. I know some view Ghostty as competitive to Warp at a GUI level, but the goal was always to empower other terminal apps via libghostty and there was no other vehicle to get that out than to build a GUI too (similar to Alacritty and their vte crate). I don't think I've ever talked negatively about Warp online (except maybe the login thing they fixed ages ago), I've always respected that they're trying something different. I know Warp has moved on to being a much bigger vision than "just" a terminal, but let's modernize that terminal core. :) github.com/Uzaaft/libghos…

@thesherlocker No as I said in my post my return would be predicated on technical merit. I’ll come back when the product and platform improve. But Kyle gets it

@mitchellh Would, in such a circumstance of a correction of direction and stabilization of engineering priorities, your decision to move away change? Or do you think the ship's already sailed?

I’ve interacted with Kyle at GitHub for close to a decade. I agree. He has my support and he’s one of the few who through all the highs and the lows really felt like understood what I was going through. He should be CEO, if one were to exist.