Shipped major updates to Git ‘n’ Coffee (aka Caffeinated Code Forge) to support Change IDs and Jujutsu (jj).
Also hashing Git commit metadata to generate Change IDs for Git commits as well. This works pretty well, but still hoping Change IDs will be added to Git in the future.
@msimoni It’s fine for depth=1 fetches, otherwise there could be hundreds of similar blobs depending on history depth. Can increase size significantly.
@msimoni Packfile is mostly objects joined together, with deltas for compression. With loose objects I don’t think there is delta compression, so it’ll require downloading similar blobs multiple times.
Repositories can now be fetched over HTTPS.
It's a custom server implementation and doesn't call git process in the background, unlike most forges.
In my tests it clones faster than the standard git daemon. Also just for fun, GitHub comparison.
Improved how diffs are rendered. And updated color scheme, that should fit into overall design better.
I like how "Gofmt's style is no one's favorite", it feels the same with so many choices of color schemes.
Just need something that works reasonably well.
@nicbarkeragain It also feels wrong to comment on AI code, like why do I care about details and quality and want to slow down shipping features, when agents can rewrite and overwrite it later anyway.
Seeing nice interactive landing pages was impressive because it showed skill and creativity of their authors.
But now since they’re easy to generate, that value is no longer there, and possibly an opposite signal. Simple pages with concise text are all that’s needed.
White AI can draft a first version of a prototype, in most cases, it isn’t the code quality I would commit to production or agree to maintain. Also I find good performance code is very hard for AI to do. Maybe that’ll change, but it’s not there yet.
This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.