nickisnoble

Joined 4 years ago

Karma
111
Submissions
55
Member since
Oct 30
https://nicknoble.works
View on Hacker News

Recent submissions

Comment · 20 days ago
Comment · 2 months ago
Pushed a fix, let me know if it hasn't improved for you.
Comment · 2 months ago
We have a multi-season arc already planned, with at least 4 unannounced characters

⋆˚.⋆⋆˚.⋆

Comment · 2 months ago
We're about to push a change that should improve this a bit, thanks for the reports!
Comment · 2 months ago
Filed a bug, looking into it!

Edit: a fix is in review

Comment · 2 months ago
I'll have it stop on non-homepages, it should also respect reduce-motion.

Any other reccs?

Comment · 2 months ago
:octopus:!
Comment · 2 months ago
It's hard to tell since any given dev can just use jj locally, if they want to, while everyone else uses git.
Comment · 2 months ago
Thanks!

There will be a lot more of it soon :D

Comment · 2 months ago
Same, it's fantastic, and SIMPLE.

Very rare these days.

Comment · 2 months ago
Big Walk is pretty close to a myst.
Comment · 3 months ago
Searchable

Log of

All

Communication &

Knowledge

Comment · 6 months ago
Easy: `jj log -n 25`

(Default is 10 iirc, so if you want 15 more... 25)

If you want everything, ever: `jj log -r ::`

Or every ancestor of your current change: `jj log -r ..@`

Comment · 6 months ago
I thought the same until I started using it.

Turns out, git sorta trains you to be very, very afraid of breaking something.

jj answers this in a few ways:

1. everything is easily reversible, across multiple axes.

2. yes, everything is basically a stash, and it's a live stash — as in, I don't have to think about it because if it's in my editor, it's already safely stored as the current change. I can switch to a different one, create a new one, have an agent work on another one, etc, all without really caring about "what if I forgot to commit or stash something". Sounds like insanity from a git POV but it really is freeing.

3. Because of 2, you can just leave conflicts alone and go work on something else (because they are, like you said, essentially stashed). It's fine and actually very convenient.

The thing the article doesn't mention, that makes this all safe, is that trunk / "main" is strictly immutable. All this flexibility is *just* for unmerged WIP. (There are escape hatches though, naturally!)

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton