Use the Neovim extension for VScode. It requires you to have Neovim installed, but it works way better then the Vim extension since it passes commands to neovim instead of using emulation.

It's funny because I miss this one all the time. I got use it in Sublime and VScode before making the jump to Neovim. I know you can get similar functionality from macros and what not, but it's just not the same.

"Google is doing this thing that is total bullshit, but now they're given you slightly less shit. What a win! Our glorious corporate overlords are so generous!"

What a joke. It's not a journalist job to shill for corporations

Please don't fulminate on HN. The guidelines make it clear we're trying for something better here. https://news.ycombinator.com/newsguidelines.html

I try to be fair minded, but some things warrant strong reactions in my opinion. Journalists shilling for corporations exerting more control over a platform they already have too much control over is one of them.

The mods or whoever are welcome to remove my comment if they think it's too far out of line.

You're literally replying to "the mods" .

Lol. Wasn't paying attention, my bad.

It's called the door-in-the-face technique. You ask for ten times what you want and get told to fuck off (the other person slams the door in your face). Then you ask for what you actually want, and having just told you to fuck off with the larger request, the other person is more likely to say yes to the smaller request.

The linked tweet leads to another tweet which leads to an article that doesn't say anything about OpenAI. It's talking about a new compression algorithm from Google potentially making memory usage 6x more efficient for LLM workloads.

Yeah that confused me, but the compression paper also doesn’t make a ton of sense since I doubt Google would have released it if it was actually such a competitive advantage compared to what other labs are doing. So I wonder what’s actually causing the price decrease.

Because humans make design decisions, AI just bangs it's head against the problem until it gets something that "works".

I'm sure it's a comfort to the parents and families of 150 dead kids that this is actually a very low error rate.

Probably vide-coded their infrastructure

Been saying this for a while now. I work in aerospace, and I can tell you from first hand experience software engineers don't know what designing a spec is.

Aero, mechanical, and electrical engineers spend years designing a system. Design, requirements, reviews, redesign, more reviews, more requirements. Every single corner of the system is well understood before anything gets made. It's a detailed, time consuming, arduous process.

Software engineers think they can duplicate that process with a few skills and a weekend planning session with Claude Code. Because implementation is cheaper we don't have to go as hard as the mechanical and electrical folks, but to properly spec a system is still a massive amount of up front effort.

And software isn't as constrained by physics as hardware, which massively expands both the design space as well as how many ways things can go wrong.

Great write up, had to bookmark so I can go through it more later there so much good stuff in there.

For the CTRL + R tip, you can make it even better if you install fzf. Massively improves searching through history. It's worth the install just for that one feature.

Best thing I ever did as a dev was start spending more time in the terminal. Getting familiar with the tools and how they interact makes life so much easier.

I'm reading the first of the blog posts. I've never actually seen any Swift code before, but looking at the package definition I'm struck by how much it looks like Zig. I've never heard Andrew Kelly call Swift out as an influence, but it seems some Swift DNA is in Zig.

Also, brave calling it swift-claude-code given Anthropics behavior.

Interesting observation on package definitions. Languages borrow good ideas from each other all the time, and the ecosystem is better for it.

On the naming fair point, already renamed the CLI binary after an earlier comment here. The repo name is more about discoverability.

Agreed. I wasn't saying it's a bad thing, just interesting.

The thing that really stuck out to me was the dot syntax:`.SomeVariable`. I'm guessing those are enum accesses where the compiler can figure out what it is from context? It's all over Zig, and it seriously screws with me lol. I know it's a me problem, but I can never keep straight what's what.