Clojure is a really fascinating language. I tried to use it seriously on a couple of occasions, but it never completely clicked for me. Despite that, it definitely had a great impact on how I think about code.
clojure.org/about/docume...
Looks like they are ready to operate these major changes.
This is exactly the kind of product I had in mind when I wrote this: a tool adapted to the new practices, with less friction around version control, PRs, code, specs...
bsky.app/profile/magg...
I've wrote a new post on the math I use to draw procedural roads only using lines and arcs. Here is how the construction unfolds:
jj can use git as a backend and at the moment it is the only one.
All I know is that for me jj cli completely replaced git clients and I have no reason to go back.
It's not so much "will jj replace git" but "how will the other tools adapt"
Finished V3 this weekend, I'm now using it for work. A bit rough around the edges, especially around version control, but I find myself fluidly using 5 parallel claude sessions, so I'm happy with the result.
Agree, but at the same time It's reasonable to use the current best platform to built the next one
"Stacked PRs is currently in private preview"
bsky.app/profile/isol...
You're perfectly right!
google trend graph for the word "harness" for the past five years. Usage starts increasing at the beginning of november
google trend graph for the word "harness" for the past year. Usage starts increasing at the beginning of november
I'm late to everything, so I didn't notice the frequent usage of the word "harness" until recently.
Apparently it started in november.
One thing I find useful when writing specs for a coding agent is to explicitly define a vocabulary upfront.
I don't know if it makes the agent perform better, but it definitely helps write a clearer document.
Lie for the keys used for sorting, add a 0.0001*index
Can you reorder in css rather than in the dom ?
Do you plan to attend local-first conf?
Yes, it's just SDFs in glsl, I don't know if there is a more elegant way to do that. Any idea?
I loved building pre react!
The web is catching up with Flash
If, like me, you wake up every morning wondering what the Voronoï diagram of arbitrary shapes looks like, here is the answer:
Github does many things, so it probably won't be one big replacement, but if many apps do some of these things correctly (stacks, specs over code...), at some point one will impose its standards.
And at the moment people seem to be willing to try many new things, so that could happen quickly.
- we interact with code differently because of AI. (Specs and plans first, we read the code less)
- stacked PRs tools improve the PRs and code reviews practices
- jj shows that we can have a far better model than git
Github is dying. It won't disappear suddenly, but unless they do major changes soon, it will be like facebook: still here, but we open it less and less.
Maybe it will survive as a pure code storage.
The replacement is not exactly here, but there are some changes
I can't find the original mention of this, but it has been observed that when you use a tool to build itself, it tends to self-destruct
This morning I'm vibing a chain of increasingly complex programming tools.
I'm at V3.
V0 was... nothing. Just claude in the terminal
V1 was useless beyond any reason.
When trying to improve V2 from itself, claude thought it would be great to restart the app, effectively killing the session 🙃
A 2026 version of emacs would be a self-building IDE where you prompt an AI to add modules specialized for the work you are doing.
One thing I learned working on a drawing app is that vector and raster graphics are much more compatible than I thought.
Once you have layers, you can perfectly interleave vectors and pixels. Affinity is doing exactly that.
New post released! 🎉
I’m breaking down everything I’ve learned about the push-pull algorithm in Signals.
It's an important publication for me, this article required more research and creativity than my previous posts. Enjoy!
→ willybrauner.com/journal/sign...
#signals #frontend #article
I had an excellent understanding of the algorithm for all these years but actually implementing it (with no help of AI in any way) gives a very different appreciation.
It is a very very beautiful algorithm.
After many attempts over years and years, I finally managed to implement Fortune's algorithm for Voronoï diagrams.
The step by step visualization was key to debug the process, and when everything work it's just mesmerizing.
JJ turned me from "uh let's delete the whole directory and clone the repo again" to "hey let's rebase these 5 branches at once! Wow, look at how my history is clean now!"
