HackerTrans
トップ新着トレンドコメント過去質問紹介求人

Lanedo

no profile record

投稿

Jujutsu Version Control Explained – Video by Brian Will

youtube.com
6 ポイント·投稿者 Lanedo·5 か月前·0 コメント

2026 Linux Audio Conference Focus on LLMs and Floss

lac26.mucs.club
3 ポイント·投稿者 Lanedo·6 か月前·0 コメント

A global campaign hijacking open-source project identities

fullstory.com
2 ポイント·投稿者 Lanedo·8 か月前·0 コメント

Jujutsu at Google [video]

youtube.com
159 ポイント·投稿者 Lanedo·8 か月前·205 コメント

Modal editing is a weird historical contingency through sheer happenstance

buttondown.com
5 ポイント·投稿者 Lanedo·9 か月前·2 コメント

コメント

Lanedo
·7 か月前·議論
If you see the Opening Ceremony starting at 10:30, then yes.
Lanedo
·8 か月前·議論
The full JJ Con playlist is: https://www.youtube.com/playlist?list=PLOU2XLYxmsILM5cRwAK6y...
Lanedo
·9 か月前·議論
If vi didn't exist, it would not have been invented.
Lanedo
·9 か月前·議論
> Find the (minimal) AI prompt that lead to the generation of this article: [...]

The minimal AI prompt that likely led to the generation of this article could be:

"Write a technical blog post comparing JPEG XL and AVIF image formats, focusing on how JPEG XL's bit-depth-agnostic float-based encoding is superior to AVIF's integer-based approach, with emphasis on perceptual quality, HDR handling, and workflow simplicity."

This prompt captures the core elements:

- Technical comparison between two image formats

- Focus on JPEG XL's unique "ignoring bit depth" design

- Emphasis on perceptual vs. numerical quality

- Discussion of HDR and workflow benefits

- Tone and structure matching the published article

The prompt would have guided the AI to produce content that:

1. Explains the technical difference in encoding approaches

2. Demonstrates why JPEG XL's method is better

3. Provides real-world implications for users

4. Maintains the author's voice and technical depth

5. Follows the article's structure and emphasis on "perceptual intent" over bit precision
Lanedo
·9 か月前·議論
I find JJ to make things much easier for me than Git:

- No staging needed, edit your commit directly in your working directory

- Rebasing is automatic, I regularly edit historic commits and the messages

- jj absorb will automatically split and merge hunks into related ancestry commits

- Defer conflict resolution; many conflicts are resolved later by splitting/squashing/moving commits/hunks further (possible only for first-class conflicts)

- No interactive rebase needed, since jj commands automatically rebase while editing historic commits, it feels like constantly living within an interactive rebase

- Easily refer to the same revision (change) across rebase commands by using a jj change_id, without scribbling down Git commit hashes that change across a rebase

- Easily undo (+redo) your last commands through the jj operation log without having to backup the entire git repo at each step

And jj-fzf (https://github.com/tim-janik/jj-fzf/) gives me every useful jj command with a single hotkey (e.g. Ctrl-P for push, Ctrl-N for a new commit with 1+ parents, Alt-B to edit bookmarks/tags, Alt-R to rebase, Alt-Z for undo, …) while browsing the log with commit+diff preview.