Cool.

4 of these are TUIs. I built Codiff specifically because TUI review became overwhelming to me. One of them is a web view, I prefer a native app window (it’s JS either way, ofc).

Also, I never wasted time building todo apps. Now I can build apps that help me do my job that I wouldn’t have had the time for without AI.

Kids these days. Calling JS "native" makes my stomach ache, but apparently this is normal.

1. I’m older than you. 2. I said native app window, comparing it to a tool with a browser web ui.

1. Why are you saying that ? Looking at your LinkedIn I'd say you're in your 40s, so effectively younger, lucky you !

2. Still, JS in the app window is not what I call native, but I won't fight over this

1. I am not in my 40s, but I take it that I was wrong ;)

Codiff is faster and scales to larger commits than those.

You're seriously suggesting that an electron app you vibe coded in two days is more performant than native code that's been developed and improved and tweaked over literal decades?

Yes. It’s built on diffs.com and trees.software.

there's a small directory tracking these — vibcod.dev. free to submit, each listing shows stack, models used, and a vibe-index score.

There is a screenshot in the README.

There is a video here: https://x.com/cnakazawa/status/2055881241677668637?s=46&t=BS...

It works for any staged, unstaged or untracked file in a repo. It does not have support for mutations (like staging or unstaging a change) yet. It does not yet work for specific commits but should be super easy to add.

That’s awesome! I built this specifically as a GUI because it’s become too much code to effectively review in the terminal for me.

exactly. LLM code output is so high that it has become unreasonable to review the code in terminal or ide

Yes you can. Check out https://fate.technology

Yeah but its react library, I talk about standard like OpenAPI schema but with GRPC model and discovery that can auto build a model response and inject it to most programming language

You don't have to rename the variable. You can also do this:

```

export function PostCard(props: { post: ViewRef<'Post'> }) {

  const post = useView(PostView, props.post);

}

```

If you add a few aliases (that can be easily generated), it becomes this:

```

export function PostCard(props: { post: PostViewRef }) {

  const post = useView(PostView, props.post);

}

```

There are many bits in fate worthy of criticism. Naming and typing React props really isn't one of those.

tRPC is just what fate starts out with. Come and contribute and we’ll have oRPC support in no time!

No. I did want to pick something facebook inspired though. I like fate because: * facebook’s original developer conference was f8 * It kinda works well for fulfilling (data) requests * It’s similar to face * It’s short and memorable

I forked a JS library for liquid-glass and patched it up with some positioning fixes. It's fun to use in presentations.

See https://github.com/nkzw-tech/liquid-glass

Nice! I like yours more