mi_lk

There's always reader mode when an author tries to be cute about their layout

So: Squash everything together then pick each component out by squash -i to an empty commit.

Seems straightforward, wouldn’t call it special

Not sure about the story but it would be funny if pi folks actually own this domain.

> Bun has had an extremely high amount of crashes/memory bugs

Any stats/source? Not that I think it's false

> and the ugly parts look uglier (unsafe) which encourages refactoring.

Looks like Bun owes that to itself to some extent, not solely because of the language

Imaging title it "Bun is being ported from Zig to Rust in an experimental branch" though. Not enough drama with that

arguably Zig started the trend just about the time GH really gone shit (this year)

Being pragmatic means admitting AI is unstoppable whether you like it or not. Stopping copilot BS doesn't conflict with that

I don't know why but this feels very English. Love it

top two both finished sub-2, just crazy

> If I'm doing something more complex and storied to the point it requires stacks with dependencies, then I'm questioning why I haven't split and chunked the thing into smaller PR's in the first place and having those reviewed.

It looks like you see stack PR as an inherent complex construct, but IMO splitting the implementation into smaller, more digestable and self-contained PRs is what stack PR is about

So if you agree that is a better engineering practice, then jj is only a tool that helps you do that without thinking too much about the tool itself

Fine tuned from Kimi. And they were not upfront about it until they got caught

restaurant name if you want to share?

I'd really like to hear your argument about when single large PR is better than stacked PRs from both PR author and reviewers' perspectives

I don't think D3 uses grammar of graphics model?

Please update the "Stacked PRs" workflow article Steve...

unironically Zune is goated in its own way

How is the bar-to-map transition done? With what framework or calculated manually

The guy has a point

that's a company built on top of Jujutsu, not jj itself

> That said, if you are starting out - I'd suggest starting with jj instead of git

That wouldn't be my advice if you're going to work with other people. You can't know jj without knowing git well enough to fall back in general

video link?

What are the tradeoffs compared to standard Go?

I would recommend WireGuard as well, I primarily use it with Tailscale as backup. WG is straightforward to set up, and with LLM the knowledge gap is now nothing if you have trouble with it

> I'm convinced that this project has got 2 things absolutely spot on. TypeScript and Worker plugins.

Can you explain why TS is spot on?

I haven’t done it specifically but it shouldn’t be much different from other tools calling

I didn't have good experience with excalidraw-mcp when it first came out a month ago; the Claude-generated diagrams were too raw/unpolished. I'm sticking to mermaid for now but I'm interested in hearing how people make exclidraw-mcp work for them

> The author of NeoVim (Thiago de Arruda)

I've always wondered what this legend is doing now

> - d21b8c949ad7 pack: add built-in plugin manager `vim.pack

Can someone try to sell me this over lazy.nvim? I asked Claude to convert lazy config to pack and I was not happy with it because how verbose it turned out

That’s really because Chris Lattner was at Google Brain at the time. Don’t think it ever took off in meaningful ways

Keep it up, I think you’re onto something. Sus