nickisnoble

Have you seen the newer variable demo? https://typeset.djr.com/?ff=input&l=1.362&u=px&s=20&c=85a44d...

Pushed a fix, let me know if it hasn't improved for you.

We have a multi-season arc already planned, with at least 4 unannounced characters

⋆˚.⋆⋆˚.⋆

We're about to push a change that should improve this a bit, thanks for the reports!

Filed a bug, looking into it!

Edit: a fix is in review

I'll have it stop on non-homepages, it should also respect reduce-motion.

Any other reccs?

:octopus:!

It's hard to tell since any given dev can just use jj locally, if they want to, while everyone else uses git.

Thanks!

There will be a lot more of it soon :D

Same, it's fantastic, and SIMPLE.

Very rare these days.

Big Walk is pretty close to a myst.

Searchable

Log of

All

Communication &

Knowledge

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 ..@`

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!)

2018 when it was just a structured editor for wikis, with basic relational databases.

(Databases was, and still are, a bit half-baked but the thing was relatively fast & powerful vs say Confluence or Apple Notes)

Nice work!

It's still not great, but it's better than anything else.

Best results when:

1. run /init and let it maintain a CLAUDE.md

2. Ask it to run checks + tests before / after every task, and add those commands to the "no permission needed list" – this improves quality by a lot

3. Ask it to do TDD, but manually check the actual test is correct

4. Every time it finishes something solid: git commit manually, /compact context (saves hella $$$ + seems to improve focus)

Honestly I treat it like a junior programmer I'm pairing with. If you pay attention, you can catch it being stupid early and get it back on track. Best when you know exactly what you want, it's just boring work. It's really good with clear instructions, eg "Refactor X -> Y, using {design pattern}."

But... Skala?!

LOL do people even google

https://www.rabbit.tech/

Edit: Seriously your SEO is going to be impossible / ridiculously expensive https://www.taskrabbit.com/

Ruby only has methods and everything is an object. So… that solves that.

Win stupid prizes.

... and then what?

Any chance you'd share the docs for that?

emacs shortcuts are unintuitive by modern reference points, it's hard to learn.

M-x === hit x and the ESC key (of all things) at the same time?

Which is not far from Aberdeen, where they test a ton of very secret stuff, like nerve gas, ENIAC, agent orange, and LSD, because it's the HQ of ATEC https://en.wikipedia.org/wiki/United_States_Army_Test_and_Ev...

Some people never learned about pointers / pass by value vs reference and it shows