_steve_yegge_

I love this take. I think what you're describing is very much happened with the Industrial Revolution. It was just a bunch of powerful, dangerous machines at first, doing small jobs faster. Scaling it up took the whole planet and a long time.

I think we are at the beginning of the second such journey. Lots of people will get hurt while we learn how to scale it up. It's why I've gone with dangerous sounding theming and lots of caution with Gas Town.

I only think it takes 2 years this time though.

Yes, that's exactly why I chose it. It starts with an 'e' and it's not a super common spelling, so it wasn't taken.

I'm sorry it's not working. I've used emacs for almost 40 years and I'm definitely contributing to it being worse, by uploading efrit in its current state. But people were asking me for it. Damned if you do and all that.

I'm more than happy to work with you to get it working, with the caveat that it actually kind of sucks right now. It's no Claude Code. But I am quickly evolving it in that direction.

Congrats on getting it running! This thing is a huge POC (and arguably a POS) so be careful with it.

It's terrible at multi-step tasks right now. I'm evolving it to work more like claude code.

Yeah it really kind of sucks right now, it's more of a proof of concept.

I'm working on evolving it into something that's not so transactional -- it will work more like claude code. Didn't realize it was going to hit the front page today. I'll poke at it this weekend and send an update.

Couldn't have put it better myself. It's great for the problems nobody has ever had time to solve. It's the problems that fall just below the ROI threshold, that tend to pile up until you have hundreds to thousands of them, each with icky weird dependencies that are _exactly_ the reason nobody has time to work on them.

Now you can chip through a dozen of these complex issues a day, and hope has finally arisen for getting through the backlog. That's a life-changing difference for anyone with a legacy code base.

Gene and I would like to invite you to review our book, if you're up for it. It should be ready for early review in about 7-10 days.

It seems like you would be the perfect audience for it. We're hoping the book can teach you what you need in order to have all those success stories yourself.

I love this!

I guess I've been summoned.

We're primarily focusing on VSCode, IntelliJ and Neovim for Cody. Of course I'll be working on an Emacs version, but that's kinda best-effort for now.

As for the new crop of codegen models, they seem to be getting to parity with GPT/Claude/Bard-class models for code autocompletions, but not so much for other tasks.

We're working on incorporating OSS models, but I'd be surprised if they're ready for prime-time this year. I think next year they'll be huge.

Just my $0.02, take with a grain of salt. Shit moves fast.

Kythe was slightly after my time on Grok. It was a side-effort by the Grok team, and it's frankly a miracle they got it out at all. Google only really supports a few big open-source projects - Chrome, YT, k8s. Kythe fell waaaay below the line.

I'll be taking another look at Kythe, and reaching out to the current Grok team, as we expand scip. But ultimately it didn't matter what protocol/format we standardize on. We just need to standardize. So it's scip!

Oh, I'm still writing it. The next installment is a novel. Thank you for your interest. :)

Howdy! Boy, HN is terrible at recovering old accounts, so I made this new one.

I just posted an update to the predictions post, with my own scores. Take a look!

As far as blogging goes, I've been on a bit of a hiatus. There's been a lot to learn. The tech world is moving so fast! I've been in Google Cloud Platform for the past 3 years, and next year I hope to start blogging about the experience, and about the technology in general.

For now, though, I'm busy both with my day job at Google and with various personal projects, so there's not much to report just yet. I promise I'll be back someday. :)