Firefox with uBlock Origin. Nothing else comes close.

That might be a good fit considering who's in charge today.

What makes Crush fun?

It has a CLI component and a very flashy TUI application. The TUI has lots of effort put in to layouts, color, and really pushing the boundaries of what a TUI can be. It looks a bit “hacker in a 2000s movie” except with pink instead of green as the dominant color.

Totally not for everybody though. I can see why some people would hate it.

You should be able to use the normal git gutter as long as your repository is colocated.

I've been using it in relatively the same way for a while now. The only meaningful changes were native support for `tug` and `absorb`, neither of which significantly changed my workflow.

eh, there have been a good amount of breaking changes. `-d`/`--destination` → `-o`/`--onto` (the former isn't yet deprecated though); deprecated `--allow-new` on push (or, forcibly making it the default for `--bookmark`); deprecated `jj bookmark track foo@bar` (and `jj bookmark track foo` having a really-weird system (I personally just call it broken, even though the behavior is intentional) of sometimes tracking the bookmark on all remotes; really I'd call jj's entire system of bookmark tracking/pulling/pushing quite incomplete outside of the trivial cases); various changed revset functions over time that break configs; and a really-annoying thing of `jj git fetch` sometimes abandoning ascendants of `@` leaving you in a confusing state (if not one with conflicts), with the solution being a future `jj git sync`.

It's certainly very usable despite all that, and the changes are simple enough to adapt to, but it's a pretty new thing.

I think for a real neophyte jj will be fine especially when used with the git backend.

Someone who "knows enough to be dangerous" may be better served by sticking with the git happy-path.

Of course, if working with others you should use what they do until you're confident that you can switch without impacting them.

Typst is amazing, but if you want HTML output, it's not quite there yet.

You don't need to subscribe to the NYT to play the games. There's a separate subscription.

I usually use Python or Rust for CLIs, but Optique makes me want to try out Typescript!

If you use a type checker in strict mode (e.g. pyright with "typeCheckingMode: strict") and a linter with strict rules (e.g. ruff with many rules enabled), the output space is constrained enough that you can get pretty consistent Python code. I'm not saying this is "good Python" overall, but it works pretty well with agents.

Who closes the gate? Is it Claude itself after it runs the verification? Who makes sure the verification did in fact run?

I usually have Claude confirm with me but I've seen it close it if its a unit test that passed for example.

You can't trust it 100%. Sometimes it will just refuse to fix a compiler or lint warning (often saying "This was a pre-existing issue...") or write a trivial test that does nothing and always passes.

> writes code with a lot of warnings > compacts > "This was a pre-existing issue..."

I still take this over writing code myself though.

I'm not saying you shouldn't. I'd say 70% of my work code is written by Claude Code or Codex. But this is something you should be aware of when interacting with agents.

Point being that there are multiple gates to one story, including human testing as one of them.